nvme_mi_aem_get_next_event(9)

✨ nvme_mi_aem_get_next_event ✨

okay bestie, welcome to the libnvme API manual, section 9 — yes this is a kernel/API manpage and yes we're gonna make it cute 💅

🌸 NAME 🌸

nvme_mi_aem_get_next_event — get the deets for the next event so you can parse it 🎀

---

🦋 SYNOPSIS 🦋

struct nvme_mi_event * nvme_mi_aem_get_next_event (nvme_mi_ep_t ep );

---

💖 ARGUMENTS 💖

• ep — the endpoint that's holding the event, like the one carrying the tea 🫖

---

🌈 DESCRIPTION 🌈

so like. when you're chilling inside an aem_handler, you call this function and the struct pointer it hands back gives you all the details about the event info. iconic behavior honestly.

It'll return NULL when the end of parsing has occurred — that's your signal that you've reached the last one, no more events, that's a wrap ✨.

⚠️ MAJOR heads up bestie, do not skip this: spec_info and vend_spec_info must be copied if you want them to persist. They are not valid after the handler_next_action has returned. Like, the moment that handler comes back, those pointers are giving expired-milk energy 💀. Copy them, periodt.

---

👑 RETURN 👑

Pointer to the next nvme_mi_event, or NULL if this one is the last one 🌸

---

and that's the whole page, you ate that 🫶 This lil writeup lives in the libnvme API manual and it's dated August 2026 — yeah, future vibes, we're ahead of the game 🦋💜