nvme_scan_ctrl(2)

✨ nvme_scan_ctrl ✨ (it's giving "scan on a controller")

okay bestie so this is nvme_scan_ctrl, and she lives in the libnvme API manual, section 2 🎀 — that's the syscalls/functions girlies, iykyk.

---

💅 NAME 💅

nvme_scan_ctrl — Scan on a controller 🦋

---

🌸 SYNOPSIS 🌸

nvme_ctrl_t nvme_scan_ctrl (nvme_root_t r , const char *name );

like… that's the whole thing. one function. one job. she's focused, she's unbothered, she's iconic. ✨

---

🎀 ARGUMENTS 🎀

• r — an nvme_root_t object 💜 that's your root, your home base, the girl everything gets attached to.
• name — Name of the controller 🫶 aka the string you're gonna hand her so she knows which controller we're talking about.

---

🔥 DESCRIPTION 🔥

So here's the tea: she scans a controller with the sysfs name name and adds it to r. 🌈

That's it. That's the whole vibe check, no cap. sysfs name in, controller added to your root out. lowkey a glow-up for your root object, fr fr. 💖

---

⭐ RETURN ⭐

Returns an nvme_ctrl_t object 💅 — the controller you just went and scanned, handed right back to you. obsessed. 🧚

ngl bestie, this one's short and sweet — no wild caveats, no dramatic warnings, just a cute little scan-and-attach moment. 🙈

---

and that's the whole page, periodt. 💜

signing off from the libnvme API manual 💖 dated July 2026 🎀 — nvme_scan_ctrl, section 2, she ate and left no crumbs. ✨🦋👑