nvme_mi_adm..._log_fw_slot(2)

✨ NAME ✨

nvme_mi_admin_get_log_fw_slot — bestie, this is the one that Retrieves the controller firmware log 💖

(also hi, you're reading the libnvme API manual, and this page is literally about one function, so cozy up 🫶)

---

🌸 SYNOPSIS 🌸

int nvme_mi_admin_get_log_fw_slot (nvme_mi_ctrl_t ctrl , bool rae ,
       struct nvme_firmware_slot *fw_log );

okay so it's giving "three arguments, one dream" 💅

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller to query. like, which one are we stalking today bestie 👀
• rae — Retain asynchronous events ✨ (yes it's a bool, no we're not elaborating, it's just vibes)
• fw_log — User address to store the log page 📥 the place where the tea gets poured

---

🦋 DESCRIPTION 🦋

This log page describes the firmware revision stored in each firmware slot supported 🔥 Think of it as a little yearbook of every slot your controller has.

The firmware revision is indicated as an ASCII string — so, plain text, no cap, exactly like that 🧚

The log page also indicates the active slot number 👑 so you always know which one is out here being the main character.

---

💜 RETURN 💜

It hands you the nvme command status if a response was received (peep enum nvme_status_field for the deets) — or -1 with errno set otherwise 😭 so yeah, check that errno, bestie, it's literally telling you what went wrong.

---

no cap: if you get -1, that errno is not decoration, go read it 🙈

---

and that's the whole page, periodt 💅 written up in July 2026 for the libnvme API manual, slay, go read your firmware slots 🌈⭐