__unregister_chrdev(9)

✨ __unregister_chrdev(9) ✨

okay so bestie, you know how I keep saying "the manual name is Kernel API Manual"? yeah. this one's a kernel API page, section 9, and it's literally the cleanup girl of the char device world. let's get into it 💅

---

🎀 NAME

__unregister_chrdev — she unregisters and destroys a cdev. both. at once. iconic behavior tbh 💖

---

🌸 SYNOPSIS

void __unregister_chrdev (unsigned int major , unsigned int baseminor ,
       unsigned int count , const char *name );

note the void — she returns nothing, she just does it. main character energy fr fr ✨

---

🦋 ARGUMENTS

• major — the major device number. the big one. the headline. 🔥
• baseminor — the first of the range of minor numbers. like, where the minor party starts 🎀
• count — how many minor numbers this cdev is occupying. the whole squad, headcount included 💜
• name — the name of this range of devices. she has a name and everyone knows it 👑

---

💖 DESCRIPTION

so basically: unregister and destroy the cdev occupying the region described by major, baseminor and count. that's the whole vibe check. she takes that region, unregisters it, destroys the cdev, done.

and the way that she's the literal opposite of __register_chrdev? this function undoes exactly what __register_chrdev did. no cap. registration girlies could never 🙈

ngl, since she destroys the cdev, treat her like a goodbye, not a "brb". don't come back expecting the device to still be sitting there 💀

---

🌈 SEE ALSO

all the siblings and cousins, straight from the kernel file ./fs/char_dev.c:

• register_chrdev_region(9)
• alloc_chrdev_region(9)
• __register_chrdev(9)
• unregister_chrdev_region(9)
• cdev_add(9)
• cdev_set_parent(9)
• cdev_device_add(9)
• cdev_device_del(9)
• cdev_del(9)
• cdev_alloc(9)
• cdev_init(9)

go read them, they all ate 💅

---

and that's the page!! 🫶 source lives in ./fs, dated October 2026, and it's __unregister_chrdev(9) forever and always — mwah, love u, go unregister responsibly 🧚⭐