Skip to content

docs: Drop dangling instruction in endpoint recovery #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 16, 2024
Merged

docs: Drop dangling instruction in endpoint recovery #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/endpoint-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -369,8 +369,6 @@ The general strategy for tracking endpoint lifecycles is [as follows]
2. Issue a call to `GetManagedObjects` `org.freedesktop.DBus.ObjectManager` on
`/au/com/codeconstruct/mctp1` for initial population of local data-structures

3. Issue

### An example order of MCTP device events, consumed by `nvmesensor`

1. A series of events yields a new FRU EEPROM device on an I2C bus already
Expand Down