libnvme_mi_open_mctp(9)

💜 libnvme_mi_open_mctp(9) 💜

okay so bestie, welcome to the libnvme API manual — this little page is all about libnvme_mi_open_mctp, and honestly? it's a whole bop. let's get into it 🫶

---

✨ NAME ✨

libnvme_mi_open_mctp — create an endpoint using a MCTP connection. that's it, that's the vibe ✨

---

🌸 SYNOPSIS 🌸

struct libnvme_mi_ep * libnvme_mi_open_mctp (struct libnvme_global_ctx
*ctx , unsigned int netid , uint8_t eid );

look at that signature, it's giving function goals 💅

---

🎀 ARGUMENTS 🎀

• ctx — your struct libnvme_global_ctx object. the main character of the whole operation, ngl 🌟
• netid — the MCTP network ID on this system. unsigned int energy, love that for you 🦋
• eid — the MCTP endpoint ID. tiny lil uint8_t, big responsibilities 😤

---

💖 DESCRIPTION 💖

so this is the transport-specific endpoint initialization for MI-connected endpoints. basically it does the MCTP-specific setup work so you don't have to think about it 💅

and here's the iconic part: once an endpoint is created, the rest of the API is transport-independent. meaning you can just vibe with the rest of the API and not worry about which transport got you here. slay 🔥

see also: libnvme_mi_close — because every iconic era needs a graceful exit 😭

---

👑 RETURN 👑

a brand new endpoint object for netid & eid, or NULL on failure. no cap — if you get NULL, something went sideways, so go check yourself before you wreck yourself 🙈

---

made with love, sass, and a genuine respect for MCTP 🧚✨ — this was libnvme_mi_open_mctp(9), from the libnvme API manual, dated October 2026. byeee, go open some endpoints bestie 💜🎀