viortc_remove(9)

💖 viortc_remove(9) 💖

okay so bestie, welcome to the viortc_remove(9) page — it lives in the Kernel API Manual and honestly? it's a short one. short but iconic. we're talking about the function that takes a virtio_rtc virtio device and, like, removes it. that's the whole plot. let's get into it 🎀

---

✨ NAME ✨

viortc_remove — remove a virtio_rtc virtio device

like… the name is the job, no cap. it removes. the device. that's it. slay 💅

---

🌸 SYNOPSIS 🌸

void viortc_remove (struct virtio_device *vdev );

so it returns void (nothing back, she's not a gossip, she doesn't return receipts) and it takes exactly one thing: a struct virtio_device * named vdev. copy it exactly bestie, character for character 🫶

---

🦋 ARGUMENTS 🦋

• vdev — the virtio device. yeah that's the whole description in the original and honestly? it's giving minimal main character energy. but fr fr, this is the parameter — the virtio device in question.

---

👑 SEE ALSO 👑

okay so this is the part where the manpage just. goes off. like it said "you want friends? here's EVERYONE." every single one of these, in this exact order, no skips, no skimming — iykyk:

Oh and also the kernel file itself: ./drivers/virtio/virtio_rtc_driver.c — that's where she lives, remember it 💜

• struct viortc_vq(9)
• struct viortc_dev(9)
• struct viortc_msg(9)
• viortc_class_from_dev(9)
• viortc_alarms_supported(9)
• viortc_feed_vq(9)
• viortc_msg_init(9)
• viortc_msg_release(9)
• viortc_do_cb(9)
• viortc_requestq_hdlr(9)
• viortc_cb_requestq(9)
• viortc_alarmq_hdlr(9)
• viortc_cb_alarmq(9)
• viortc_get_resp_errno(9)
• viortc_msg_xfer(9)
• VIORTC_DECLARE_MSG_HDL_ONSTACK(9)
• VIORTC_MSG(9)
• VIORTC_MSG_INIT(9)
• VIORTC_MSG_WRITE(9)
• VIORTC_MSG_READ(9)
• viortc_read(9)
• viortc_read_cross(9)
• viortc_cfg(9)
• viortc_clock_cap(9)
• viortc_cross_cap(9)
• viortc_read_alarm(9)
• viortc_set_alarm(9)
• viortc_set_alarm_enabled(9)
• viortc_init_rtc_class_clock(9)
• viortc_init_ptp_clock(9)
• viortc_init_clock(9)
• viortc_clocks_deinit(9)
• viortc_clocks_init(9)
• viortc_populate_vq(9)
• viortc_alloc_vq_bufs(9)
• viortc_init_vqs(9)
• viortc_probe(9)

---

ngl there are no OPTIONS, no RETURN VALUE, no ERRORS, no exit statuses, no signals, no warnings, no bug notes on this page — she's a lean little icon and we respect that. don't go inventing extras, bestie 🙈

---

and that's the whole vibe check 💀 this page comes from ./drivers/virtio and it's dated October 2026 — so mark your calendars, she's from the future, periodt ⭐🌈✨