libnvme_mi_submit_entry(9)

📦 version 3.2, in arch rolling

🌸 libnvme_mi_submit_entry (9) — nvme girlie edition 🌸

okay so like, hi bestie 💖 this one is from the libnvme API manual and it's honestly such a sweet little hook. it's giving "backstage pass" energy. let's go ✨

✨ NAME ✨

libnvme_mi_submit_entry — the weak hook that gets called before an MI message is sent. literally the pre-game ritual 🎀

🦋 SYNOPSIS 🦋

void * libnvme_mi_submit_entry (__u8 type , const struct nvme_mi_msg_hdr *hdr , size_t hdr_len , const void *data , size_t data_len );

no cap, that's the whole signature 💅

💜 ARGUMENTS 💜

  • type — the MCTP message type 🌈
  • hdr — pointer to the MI message header 👑
  • hdr_len — how long the message header is, in bytes 🎀
  • data — pointer to the message payload data 🍓
  • data_len — how long the payload data is, in bytes 🧚

🔥 DESCRIPTION 🔥

so this is a weak symbol, which is the whole main character thing about it — an application can override it if it wants. and like, why would you? to intercept outgoing MI messages, bestie. for tracing or testing purposes. that's it, that's the vibe check ✨

oh and super important: whatever you return? it gets passed back as user_data to the matching libnvme_mi_submit_exit call. so like, they're linked, iykyk 🫶

💀 RETURN 💀

an opaque pointer that gets passed to libnvme_mi_submit_exit, or NULL. no thoughts, just vibes 🙈

ok that's the whole page, go forth and trace your MI messages responsibly 💜

peace out bestie 💖 this has been libnvme_mi_submit_entry from the libnvme API manual, dated October 2026 — slay, periodt ✨🎀🦋

📦 where this page comes from