NVME_CTRL_IS_DISCOVERY_CTRL(2)

✨ NAME ✨

nvme_ctrl_is_discovery_ctrl — the little function that peeks at the discovery_ctrl flag and tells you what's up 💅

🌸 quick vibe check: this page lives in the libnvme API manual (section 2, bestie — the syscalls-and-library-calls girlies), so if you were looking for shell commands, wrong room, but stay anyway, you're cute.

---

🌈 SYNOPSIS 🌈

bool nvme_ctrl_is_discovery_ctrl (nvme_ctrl_t c );

That's it. That's the whole entire signature. One arg, one bool coming back at you. No cap. ✨

---

🎀 ARGUMENTS 🎀

• c — the controller you want checked. Like, this specific one, hand it over, we'll look at it. The controller to be checked, fr fr. 🦋

---

💖 DESCRIPTION 💖

okay so here's the tea 🍵 — this function returns the value of the discovery_ctrl flag. And that flag is the one that tells you whether c connects to a discovery subsystem. That's the whole plot. Lowkey iconic for how much it's not doing. 😭

---

👑 RETURN 👑

The value of the discover_ctrl flag. That's what the doc says — yes, it's spelled discover_ctrl right here, not discovery_ctrl, we noticed it too, we're not gonna touch it, that's above our pay grade 🙈.

---

🫶 SEE ALSO 🫶

(nothing in the original, bestie — this page keeps to itself, main character energy, no entourage 💅)

---

💀 no warnings, no bugs listed, no environment variables, no files, no exit statuses, no signals. This one's a chill little guy. Sip your iced coffee. 🍓

---

⭐ and that's the page!! brought to you by the libnvme API manual, dated July 2026, section 2 — nvme_ctrl_is_discovery_ctrl(2), mwah, obsessed, periodt 🧚💖