nvme_mi_adm...nged_ns_list(2)

πŸ’– nvme_mi_adm...nged_ns_list(2) πŸ’–

okay bestie, welcome to the libnvme API manual β€” this one's short but it's mighty, and it's literally just one function, so we're gonna eat this up in like two minutes. no cap. πŸ¦‹


✨ NAME ✨

nvme_mi_admin_get_log_changed_ns_list β€” Retrieve namespace changed list πŸ’…


🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_changed_ns_list (nvme_mi_ctrl_t ctrl , bool
rae , struct nvme_ns_list *ns_log );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl</p> β€” the Controller you're querying, aka the one you're asking all the nosy questions to 🫢
  • rae β€” Retain asynchronous events, so like... keep them. don't let 'em go ✨
  • ns_log β€” User address to store the log page β€” that's where the tea gets written down πŸ“

🌈 DESCRIPTION 🌈

so this log page literally describes namespaces attached to this controller that have changed since the last time the namespace was identified, been added, or deleted. it's giving "receipts of what moved" and honestly? obsessed. πŸ’€βœ¨


πŸ”₯ RETURN πŸ”₯

The nvme command status if a response was received (see enum nvme_status_field) or -1 with errno set otherwise.

no response? you get -1 and errno gets set. that's the whole mood. πŸ™ˆ

and that's the page, bestie!! πŸ’œ this whole thing comes from the libnvme API manual, and the version/date stamp? July 2026. slay, goodbye, go ask your controller what changed πŸ‘‘πŸŒΈβœ¨

πŸ“¦ where this page comes from