rpmsg_chrdev_eptdev_destroy(9)

🌸 rpmsg_chrdev_eptdev_destroy(9) 🌸

okay so this is a page from the Kernel API Manual and it's all about rpmsg_chrdev_eptdev_destroy(9) — yes bestie, a whole function, and honestly? she's a closer. let's get into it 💅

---

✨ NAME ✨

rpmsg_chrdev_eptdev_destroy — destroy created char device endpoint. that's it, that's the whole job. iconic, no notes 🎀

---

🦋 SYNOPSIS 🦋

int rpmsg_chrdev_eptdev_destroy (struct device *dev , void *data );

look at her go. returns an int, takes two args, slays 🫶

---

💖 ARGUMENTS 💖

• dev — okay so the actual manual literally says -- undescribed -- 😭 like the docs really just left her on read. no cap, that's what it says. so we move on, respectfully 🙈
• data — the private data associated to the endpoint device. that's her little personal stash of info, tied to the endpoint device fr fr 💜

---

🔥 DESCRIPTION 🔥

so what does she actually do? this function destroys a rpmsg char endpoint device — specifically the one that got created by the RPMSG_DESTROY_EPT_IOCTL control. basically she's the clean-up crew, the "you don't have to go home but you gotta get out of here" of endpoint devices. the way that she just... removes the thing that was made? highkey satisfying ✨

not me emphasising that it destroys the device created by the RPMSG_DESTROY_EPT_IOCTL control — keep that detail bestie, it's the whole point 💀

---

👑 SEE ALSO 👑

• the Kernel file ./drivers/rpmsg/rpmsg_char.h — go read the header, iykyk 📖
• rpmsg_chrdev_eptdev_create(9) — the origin story, the creator, the main character energy that makes this destroy function even possible 🌈

---

⭐ sign-off ⭐

okay that's the page!! and for the credits moment you know i gotta give it up: this one lives under the source ./drivers/rpmsg, dated October 2026, and it's filed under rpmsg_chrdev_eptdev_destroy(9). periodt 💅🎀✨