__rpmsg_destroy_ept(9)

💅 __rpmsg_destroy_ept (9) — like, the kernel API manual, but make it make sense ✨

okay so bestie, you've stumbled into section 9 of the kernel API manual — that's the "functions the kernel devs use" zone, not your regular "type man ls" zone. and today's main character is __rpmsg_destroy_ept, which (spoiler) destroys an rpmsg endpoint. the double underscore at the front is giving "internal, don't touch unless you know what you're doing" energy, and honestly? respect. 👑

---

🌸 NAME 🌸

__rpmsg_destroy_ept — destroy an existing rpmsg endpoint. that's it. that's the whole name. it destroys an ept. periodt. 💅

---

🦋 SYNOPSIS 🦋

void __rpmsg_destroy_ept (struct virtproc_info *vrp , struct rpmsg_endpoint *ept );

returns void, so like… it gives you nothing back. no status, no error code, no little note. it just does the thing and dips. iconic behaviour tbh. 🎀

---

⭐ ARGUMENTS ⭐

• vrp — the virtproc that owns this ept. think of it as the parent, the one holding the leash. 🫶
• ept — the endpoing to destroy. (yes, "endpoing" — that's the original spelling, and honestly it's kind of a vibe, we're keeping it. 😭💀)

---

🔥 DESCRIPTION 🔥

so here's the tea ☕ — this is an internal function which destroys an ept without assuming it is bound to an rpmsg channel.

read that again, because it matters: it does not assume the ept has a channel attached. that's the whole reason it exists as a separate thing from the regular destroy path.

and why do we need a destroy that doesn't assume a channel binding? because of the internal name service endpoint, which — plot twist — isn't bound to an rpmsg channel. so the normal path can't help it. this one can. 🧚

also go look at __rpmsg_create_ept — you know, the one that made the ept in the first place. the origin story. the prequel. ✨

ngl, if you're calling this from driver code and you're not living inside the rpmsg core, maybe do a little vibe check on your life choices first. it's internal for a reason, bestie. 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/rpmsg/virtio_rpmsg_bus.c — the actual source, go read it, it's lowkey good for you 📖
• struct virtproc_info(9)
• struct rpmsg_hdr(9)
• struct virtio_rpmsg_channel(9)
• rpmsg_sg_init(9)
• __ept_release(9)
• rpmsg_send_offchannel_raw(9)

like, the whole rpmsg friend group is right there. click through, it's giving lore. 🔍💜

---

and that's the page, bestie!! 🎀 no cap, you ate this. this one came out of ./drivers/rpmsg and it's dated October 2026 — so go forth, destroy some endpoints responsibly, and remember: bound-to-a-channel is a whole different conversation. mwah. 💖🦋✨