NVME_INIT_GET_LOG_MI_CMD_SUPPORTED_EFFECTS-LIBNVME3(2)

💖 nvme_init_get_log_mi_cmd_supported_effects(9) 💖

okay so real talk, the full name is nvme_init_get_log_mi_cmd_supported_effects and yes it's a whole mouthful, but we're in the libnvme API manual bestie, so we keep it iconic, not abbreviated. 🎀

---

✨ NAME ✨

nvme_init_get_log_mi_cmd_supported_effects — sets up the passthru command for MI Commands Supported by the controller, and it's giving "let me prep that log request for you" energy. 💅

---

🌸 SYNOPSIS 🌸

void nvme_init_get_log_mi_cmd_supported_effects (struct libnvme_passthru_cmd *cmd ,
                                                 struct nvme_mi_cmd_supported_effects_log *log );

two arguments, no return value (void, she's a void girlie, she just does the thing), periodt. ✨

---

🦋 ARGUMENTS 🦋

• cmd — the passthru command you're gonna use. hand it over and she'll init it for you, no cap. 🫶
• log — the MI Command Supported and Effects data structure. this is where the good stuff lives. 🌈

---

💜 DESCRIPTION 💜

so what she actually does: she initializes the passthru command buffer for the Get Log command, with the LID value set to NVME_LOG_LID_MI_CMD_SUPPORTED_EFFECTS. that's it, that's the whole vibe — lowkey simple, highkey essential. ⭐

like, you hand her a cmd and a log, she wires up the buffer so it's ready to ask the controller for the MI command supported-and-effects log. slay. 👑

ngl there's no return value here (void), so nothing to check on the way out — the setup just happens. 🧚

---

🔥 SEE ALSO 🔥

there are no SEE ALSO references in the original page — she stands alone, main character energy, no entourage. 💀

---

and that's the whole page bestie!! 🍓 source/version: the libnvme API manual, dated October 2026 — mwah, love that for us. 💖🌸✨