LIBNVME_MI_MI_READ_MI_DATA_CTRL_LIST-LIBNVME3(2)

💖 libnvme_mi_mi_read_mi_data_ctrl_list(9) 💖

okay bestie, welcome to the libnvme API manual — this page is all about one little function with a very long name, and honestly? it ate. 🫶

---

✨ NAME ✨

libnvme_mi_mi_read_mi_data_ctrl_list — does a Read MI Data Structure command and brings back the list of attached controllers. literally just vibes and controllers. 💅

---

🌸 SYNOPSIS 🌸

int libnvme_mi_mi_read_mi_data_ctrl_list (struct libnvme_mi_ep *ep ,
__u8 start_ctrlid , struct nvme_ctrl_list *list );

---

🎀 ARGUMENTS 🎀

• ep — the endpoint for MI communication. this is the connection, the main character of the whole operation 👑
• start_ctrlid — starting controller ID. like, where do we even begin, you know? this is that number 🧚
• list — the controller list to populate. you hand it over, the function fills it in. bestie does the work, you provide the vessel 💜

---

🦋 DESCRIPTION 🦋

So the way this works: it retrieves the list of attached controllers — and specifically, the ones with IDs that are greater than or equal to start_ctrlid. no cap, that's the filter. 🌈

Also, go look at struct nvme_ctrl_list if you wanna know what's actually inside. iykyk ⭐

---

🔥 RETURN 🔥

If a response came back, you get the nvme command status (peep enum nvme_status_field for that one 👀). Otherwise you get a negative error code — which is the function's way of saying "nah babe, something went wrong" 😭💀

---

fr fr, don't forget: the status is only there if a response was received. no response means negative error code, periodt. 💅

---

✨ that's the whole page, you're so welcome ✨

okay so this was the libnvme API manual page, and just so we're all on the same page, the footer says October 2026 and it's from libnvme_mi_mi_read_mi_data_ctrl_list(9) — big slay, go touch some grass now, or better yet, go read your controller list 🎀💖🦋🌸🫶👑