nvme_mi_adm...rted_effects(2)

okay so grab your iced coffee bestie ☕ because we're reading the libnvme API manual, page 2, and the star of the show is nvme_mi_admin_get_log_fid_supported_effects ✨. yes the page name got cut off to nvme_mi_adm...rted_effects and honestly? she's too iconic for a full name anyway 💅. no cap, this is the one that pulls the Feature Identifiers Supported and Effects tea.

---

✨ NAME ✨

nvme_mi_admin_get_log_fid_supported_effects — Retrieve Feature Identifiers Supported and Effects 🎀

like, that's literally her job. she goes and gets the FID supported + effects info. periodt.

---

🦋 SYNOPSIS 🦋

int nvme_mi_admin_get_log_fid_supported_effects (nvme_mi_ctrl_t ctrl ,
bool rae , struct nvme_fid_supported_effects_log *log );

yes she takes three little arguments and returns an int, main character energy 🌈

---

🌸 ARGUMENTS 🌸

• ctrl — Controller to query 👑 this is the controller you're asking, so pick the right one bestie, don't be texting the wrong group chat.
• rae — Retain asynchronous events 🫶 it's a bool, so it's giving either-coded.
• log — FID Supported and Effects data structure 🍓 this is where the whole answer lands, so hand her a real struct to fill, not vibes.

---

💜 RETURN 💜

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

so like: response came back? you get the nvme command status, and enum nvme_status_field is where you go read what that status means. no response? you get -1 and errno gets set to tell you why. lowkey rude of her but that's the deal 🙈

bestie reminder: -1 + errno is not a vibe check you want to fail. always peek at errno, fr fr.

---

and that's the whole page, no skips, we read every line 💖🧚

sign-off szn: this was the libnvme API manual, dated July 2026 🌟 obsessed with her, truly. mwah, go query a controller responsibly, ily 🫶💅