diff options
author | David Gwynne <dlg@cvs.openbsd.org> | 2014-04-16 00:27:00 +0000 |
---|---|---|
committer | David Gwynne <dlg@cvs.openbsd.org> | 2014-04-16 00:27:00 +0000 |
commit | 6c1876ab0a19fd8d65086cb8860c3a25784cc8d2 (patch) | |
tree | 425eb1f09305b63e330dcc9656463c15df595873 /sys/altq/altq_rmclass.c | |
parent | e0141c26819310ad828aa6c945e8d197a6e245c6 (diff) |
have nvme_poll return the status bigs from the completion ring
entry. if i ever implement timeouts ill use high bits in the int
or the phase bit to indicate non chip related errors. a successful
chip status conveniently maps to 0. how handy.
this lets me move the completion handling for the controller
identification commands back into the caller. at the moment im just
printing out controller and firmware details like we do on
mfi/mpii/mfii.
Diffstat (limited to 'sys/altq/altq_rmclass.c')
0 files changed, 0 insertions, 0 deletions