libnvme_ctr...scovery_ctrl(9)

πŸ“¦ version 3.2, in arch rolling

✨ libnvme_ctrl_get_discovery_ctrl ✨

okay bestie, so this is a page from the libnvme API manual β€” the header up top literally reads libnvme_ctr...scovery_ctrl(9) because apparently even manpage titles get the truncation treatment sometimes 😭 but like, the actual function we're talking about is libnvme_ctrl_get_discovery_ctrl, and ngl it's one of those tiny little getters that just… vibes.


🌸 NAME 🌸

libnvme_ctrl_get_discovery_ctrl β€” Get discovery_ctrl.

like, it gets the discovery_ctrl. that's the whole job. she's an icon, she's a simple queen, she does one thing πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

bool libnvme_ctrl_get_discovery_ctrl (const struct libnvme_ctrl *p );

no cap, that's the entire signature β€” copy it exactly, don't come for me about the spacing, that's how the manual has it 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • p β€” the struct libnvme_ctrl instance you wanna query. that's your girl, your source of truth, the thing you're asking about. it's const, so we're just looking, not touching πŸ‘€

⭐ RETURN ⭐

it hands you back the value of the discovery_ctrl field. (the return type is bool, so it's a yes/no situation, lowkey very straightforward energy.)


πŸ’– reminder: this is a getter in the libnvme API manual, so keep the exact names and types in your code β€” libnvme_ctrl_get_discovery_ctrl, const struct libnvme_ctrl *p, discovery_ctrl, bool. they're all doing their little main character thing and they need to stay spelled exactly like that ✨

and that's the whole page, bestie! short, sweet, slay. this one's from the libnvme API manual, dated October 2026 β€” so like, very much current, very much official πŸ’œπŸ¦‹βœ¨ bye pookie 🫢

πŸ“¦ where this page comes from