nvme_init_m..._port_delete(9)

💅 nvme_init_manage_export_port_delete (from the libnvme API manual, bestie 🫶)

Okay so picture this: you're deep in the libnvme API manual, section 9, and you've found nvme_init_manage_export_port_delete — yes the header is all nvme_init_m..._port_delete(9) because apparently even manpage titles need a little drama and truncation ✨

---

✨ NAME ✨

nvme_init_manage_export_port_delete — the glow-up that initializes the passthru command for Manage Exported Port - Delete 👑 literally does exactly what it says on the label.

---

🌸 SYNOPSIS 🌸

void nvme_init_manage_export_port_delete (struct libnvme_passthru_cmd
*cmd , struct nvme_exported_port_delete_data *data );

No cap, that's the whole signature. It returns void — she gives nothing back, she just prepares 💅

---

🎀 ARGUMENTS 🎀

• cmd — the passthru command you're gonna use. This is the main character of the operation, the buffer she's about to set up for you 🦋
• data — the delete data buffer, bestie. Check struct nvme_exported_port_delete_data for the deets, iykyk 💖

---

🌈 DESCRIPTION 🌈

So what does she actually do? She initializes the passthru command buffer for the Manage Exported Port command, and she sets the SEL value to NVME_MANAGE_EXPORT_PORT_SEL_DELETE. That's it. That's the vibe check, and she passed ⭐

Like, this is the "delete" flavor specifically — NVME_MANAGE_EXPORT_PORT_SEL_DELETE is right there in the name, so you know exactly which selector is getting written in there. No guessing, no mystery, just clean initialization energy 🔥

Reminder bestie: it's void, so there's no return value to check. The function's whole job is filling in that cmd buffer for you 🙈

---

🧚 sign-off 🧚

That's the page! Source and version: this is the libnvme API manual, dated October 2026 — and yeah, the footer does that little self-referential nvme_init_manage_export_portnvme_init_m..._port_delete(9) thing again because we love a consistent aesthetic 💜 Mwah, go initialize some commands, you're doing amazing 🍓💅