libnvme(9)

💅 libnvme(9) — ok bestie, let's talk about enum nvme_directive_receive_doper

So this page is from the API Manual for libnvme, section 9 — yes, that's the <pink>libnvme(9)</pink> situation, and it's literally all about one enum. One. Iconic, honestly. Small page, big main-character energy. 🎀

---

✨ NAME ✨

enum nvme_directive_receive_doper — the Directive Receive Directive Operation enum. That's right, "Directive Receive Directive Operation." It said directive twice because it can. 👑

---

🌸 SYNOPSIS 🌸

Here's the whole thing, copy-pasted with love and zero typos (fr, don't touch it):

enum nvme_directive_receive_doper {
    NVME_DIRECTIVE_RECEIVE_IDENTIFY_DOPER_PARAM ,
    NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_PARAM ,
    NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_STATUS ,
    NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_RESOURCE

};

Notice the little space before each comma? Yeah. That's just how it is. We respect it. 🫶

---

🦋 Constants 🦋

Okay so this is the part where the original man page just... lists them. No descriptions, no notes, no lore. So I'm not gonna make stuff up (that would be so not slay of me) — here are your four constants, exactly as given:

• NVME_DIRECTIVE_RECEIVE_IDENTIFY_DOPER_PARAM — no description in the source, just vibes and a very long name. 💜
• NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_PARAM — again, listed with no extra tea. 🌈
• NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_STATUS — it's giving "status," it's giving no further commentary. ⭐
• NVME_DIRECTIVE_RECEIVE_STREAMS_DOPER_RESOURCE — the fourth one, rounding out the set. ✨

Lowkey the takeaway here is: the enum exists, these are its four members, and the man page trusts you to know what you're doing. Respect. 💅

---

🧚 sign-off 🧚

That's the whole page, bestie — short and sweet, no cap. This one's dated October 2026, it lives in the API Manual, and it goes by libnvme(9) on the footer, so you know exactly where it came from. Go forth and receive some directives. 😭🦋💖