rproc_remove_virtio_dev(9)

✨ rproc_remove_virtio_dev(9) ✨

okay bestie, welcome to the Kernel API Manual 🎀 — this one's a tiny little function page from rproc_remove_virtio_dev(9) and honestly? she's short, she's sweet, she's giving "last one out, turn off the lights" 💅

---

💖 NAME 💖

rproc_remove_virtio_dev — remove an rproc-induced virtio device 🫶

like. it un-does the thing. the virtio device that rproc brought into this world? yeah, this is the function that sends it home 😭

---

🦋 SYNOPSIS 🦋

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

that's it. that's the whole signature. short king 👑

---

🌸 ARGUMENTS 🌸

• dev — the virtio device 🧚 the actual little guy we're yeeting
• data — must be null ⭐ no cap, it literally has to be null — that's the vibe check and you gotta pass it

---

🌈 DESCRIPTION 🌈

This function unregisters an existing virtio device. periodt 💅

that's the whole description. she does one (1) thing and she does it well — takes a virtio device that already exists and unregisters it. main character energy, zero notes 🔥

---

👑 RETURN 👑

0

yup. just 0. that's the return value. iconic, unbothered, returns zero 😌✨

---

💜 SEE ALSO 💜

• Kernel file ./drivers/remoteproc/remoteproc_virtio.c — go read the source, iykyk 📖
• rproc_vq_interrupt(9)
• rproc_add_virtio_dev(9) — the one that puts the device in, this page is the one that takes it out 🎀 (also: the twin flame energy is real)

---

little reminder bestie: data being anything other than null is not the move. the manpage says must be null and we respect the manpage 🙈

---

and that's the page!! 🌸 this lil gem lives in ./drivers/remoteproc and the docs are dated October 2026 💖 mwah, go unregister something responsibly 🫶⭐💅