libnvme(2)

💅 libnvme(2) — API Manual

okay bestie, welcome to the libnvme manual, section 2 of the API Manual, and today's main character is an enum. yes, an enum. and she's kind of a baddie actually. sit down, grab a lil snack 🍓, we're doing this together.

---

✨ NAME ✨

enum nvme_lockdown_log_scope — the lockdown log page scope attributes, aka what exactly are we locking down here, bestie? 🔒

---

🦋 SYNOPSIS 🦋

enum nvme_lockdown_log_scope {
    NVME_LOCKDOWN_ADMIN_CMD ,
    NVME_LOCKDOWN_FEATURE_ID ,
    NVME_LOCKDOWN_MI_CMD_SET ,
    NVME_LOCKDOWN_PCI_CMD_SET

};

like. look at her. four little constants, all in a trench coat, all describing scope values. no cap. 💖

---

👑 Constants 👑

these are the girls. every single one of them. we are not skipping anybody, periodt.

• NVME_LOCKDOWN_ADMIN_CMD — the scope value for Admin commandS. (yes, capital S, that's literally how the original wrote it and I am not touching it, it's iconic 💀). this is the "we're talking about Admin commands" scope.
• NVME_LOCKDOWN_FEATURE_ID — the scope value for a Feature ID. when the thing you're scoping is a feature ID, this is the vibe check you pass. ✨
• NVME_LOCKDOWN_MI_CMD_SET — the scope value for Management Interface commands. MI gang rise up 🫶
• NVME_LOCKDOWN_PCI_CMD_SET — the scope value for PCI commands. PCI said "I'm also part of this" and honestly? she is. 💅

---

lowkey the whole point here: every one of these is a scope value for the lockdown log page. that's it, that's the tea. no hidden lore, no extra behaviour, no sneaky defaults. just four constants being their authentic selves. 🧚

---

💜 and that's the whole page, bestie — this one came out of the libnvme(2) API Manual, page enum nvme_lockdown_log_scope, dated July 2026. mwah. go lock something down responsibly. 🎀🌸