libnvme(9)

💖 NAME 💖

struct nvme_fw_commit_event — it's the Firmware Commit Event Data bestie, literally the little receipt you get when firmware goes through a commit ✨

This one lives in the libnvme API Manual (yes, that's the libnvme(9) manual section, we're being fancy today 💅).

🦋 SYNOPSIS 🦋

okay so here's the whole struct, no cap, exactly as it is:

struct nvme_fw_commit_event {
    __le64 old_fw_rev;
    __le64 new_fw_rev;
    __u8 fw_commit_action;
    __u8 fw_slot;
    __u8 sct_fw;
    __u8 sc_fw;
    __le16 vndr_assign_fw_commit_rc;
 };

that's it. that's the vibe check. 🫶

👑 Members 👑

• old_fw_rev — the Old Firmware Revision. it's giving "before" pic energy 📸, the revision you're leaving behind.
• new_fw_rev — the New Firmware Revision. the glow-up revision, the one you're stepping into 💫
• fw_commit_action — the Firmware Commit Action. which action the Firmware Commit Command was told to do, front and center 🎬
• fw_slot — the Firmware Slot. which slot it all went down in, main character energy only 🔥
• sct_fw — the Status Code Type for Firmware Commit Command. the SCT of the Firmware Commit Command, so you know what kind of status you're dealing with 👀
• sc_fw — the Status Returned for Firmware Commit Command... wait, the status returned for the Firmware Commit Command 😭 the actual result, the moment of truth.
• vndr_assign_fw_commit_rc — the Vendor Assigned Firmware Commit Result Code. vendor's own special little result code, iykyk 🧚

fr fr, every field here maps straight to the Firmware Commit Event Data — nothing extra, nothing skipped, periodt 💀✨

and that's the whole page bestie — signed off from the libnvme(9) API Manual, in the October 2026 edition, where this icon struct nvme_fw_commit_event lives rent free 👑💜 bye!! 🎀