libnvme(9)

✨ libnvme — struct nvme_mi_mi_resp_hdr ✨

okay bestie, welcome to the libnvme(9) API Manual page 🫶 this one is short and sweet and honestly kind of iconic — it's all about the MI response message header. yes, the whole page. it's giving "one struct, zero notes" 💅

---

💖 NAME 💖

struct nvme_mi_mi_resp_hdr — the MI response message header. that's it, that's the whole vibe 🎀

---

🦋 SYNOPSIS 🦋

struct nvme_mi_mi_resp_hdr {
    struct nvme_mi_msg_hdr hdr;
    __u8 status;
    __u8 nmresp[3];
 };

look at her. three members, one generically-typed header, no cap 🔥

---

🌸 Members 🌸

• hdr — the generic MI message header. the little universal intro every message gets, fr fr.
• status — the generic response status from the command. and listen, bestie: non-zero means failure 😭 so if this isn't zero, something did NOT slay and you should probably pay attention.
• nmresp — the NVMe Management Response 💅 this is the command-type-specific response data, i.e. the part where each command brings its own main-character energy 👑

---

🌈 Description 🌈

this is the wire format for the MI response message header, defined in section 5 of NVMe-MI ⭐ so like, if you're parsing bytes off the wire, this is the exact layout you're looking at — header first, then status, then those 3 bytes of nmresp. it's giving "on the wire and unbothered" 🧚

---

💀 tiny reminder for the group chat: status being non-zero = failure. don't ignore her. she's trying to tell you something.

---

and that's the page, bestie!! short, iconic, fully documented 💜 this was the struct nvme_mi_mi_resp_hdr page from the API Manual, dated October 2026 🌸 mwah, go read some NVMe-MI spec section 5 and slay ✨🎀