nvme_mi_open_mctp(2)

✨ nvme_mi_open_mctp — bestie's guide to opening an MCTP endpoint ✨

okay so real quick, this one lives in the libnvme API manual (section 2 of the manual pages, iykyk) 💅

---

🌸 NAME 🌸

nvme_mi_open_mctp — Create an endpoint using a MCTP connection.

🦋 SYNOPSIS 🦋

nvme_mi_ep_t nvme_mi_open_mctp (nvme_root_t root , unsigned int netid ,
       uint8_t eid );

💖 ARGUMENTS 💖

• root — the root object you wanna create this thing under, periodt 🌱
• netid — the MCTP network ID on this system, fr fr
• eid — the MCTP endpoint ID 👑

🎀 DESCRIPTION 🎀

So this is the transport-specific endpoint initialization for MI-connected endpoints. Transport-specific is the key word bestie, don't skip it 🙈

And here's the slay: once an endpoint is created, the rest of the API is transport-independent. So like, you do the one little transport-flavored step here and then everything else just works the same no matter what. main character energy 🌈

Also, go look at nvme_mi_close — she's the one who cleans up after this. Don't leave your endpoints hanging, that's not the vibe 💀

🫶 RETURN 🫶

A brand new endpoint object for netid & eid… or NULL on failure 😭 (in which case, no endpoint for you, sorry bestie).

---

and that's the whole page, no cap 💜 she's short and iconic. This edition of the libnvme API manual page nvme_mi_open_mctp is brought to you from July 2026 — yes, from the future, we stay ahead 🎀✨