nvme_fc_unr...r_remoteport(9)

💅 nvme_fc_unregister_remoteport(9) — a Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual ✨ this one's called nvme_fc_unregister_remoteport and honestly it's giving "cleanup era" 🧹

---

🌸 NAME 🌸

nvme_fc_unregister_remoteport — the transport entry point that an LLDD calls when it wants to deregister/remove a previously registered NVMe subsystem FC port. yeah. she's the goodbye-girlie of the remote port world 🫶

---

✨ SYNOPSIS ✨

int nvme_fc_unregister_remoteport (struct nvme_fc_remote_port *portptr);

that's it. one call. one pointer. very main character energy 👑

---

🎀 ARGUMENTS 🎀

• portptr — pointer to the (registered!) remote port that's getting deregistered. key word: registered — she has to already exist, bestie, no ghosting ports allowed 🙈

---

💖 RETURN 💖

it hands back a completion status, fr fr:

• 0 — success, we ate, no crumbs 🔥
• a negative errno on failure — like -ENXIO for example. so if you see a minus sign, something went sideways and you should probably look into it 😭

ngl the "must be 0 upon success" part is real — that's the contract, don't be out here returning vibes instead of 0 💀

---

🌈 SEE ALSO 🌈

• the kernel file ./drivers/nvme/host/fc.c — that's where the whole squad lives 🦋
• nvme_fc_register_localport(9)
• nvme_fc_unregister_localport(9)
• nvme_fc_register_remoteport(9)
• nvme_fc_rescan_remoteport(9)
• nvme_fc_rcv_ls_req(9)

like a little friend group of function calls, honestly obsessed 💜

---

lowkey reminder: this is the transport entry point called by an LLDD — so if you're not an LLDD, this isn't your party, iykyk 💅

---

signed, sealed, delivered from ./drivers/nvme/host, dated October 2026, and stamped with the whole nvme_fc_unr...r_remoteport(9) header vibe ⭐ that's the tea, periodt 🍓🧚