component_del(9)

💅 component_del(9) — the Kernel API Manual, but make it a group chat

ok so like. bestie. you're in the Kernel API Manual and this page is component_del(9) and it's the undo button for component_add. that's it, that's the vibe. 🎀

---

✨ NAME ✨

component_del — unregister a component. literally just: you added a component, now you're removing it. it's giving "we're so back" in reverse. 🦋

---

✨ SYNOPSIS ✨

void component_del (struct device *dev , const struct component_ops *ops
);

yes queen, that's the whole signature. void return, which means it does not hand you a status code back. no notes. 💅

---

✨ ARGUMENTS ✨

• dev — the component device. (the device one, not the ops one, keep up 🫶)
• ops — the component callbacks. the ops. the whole personality. ✨

---

✨ DESCRIPTION ✨

so what this does: it unregisters a component that you previously added with component_add. simple. clean. iconic.

but here's the part where you need to sit down — if that component happens to be bound into an aggregate driver, then calling this will force the entire aggregate driver, including all of its components, to be unbound. 🔥

the way that one component_del can take down the whole squad... main character energy fr fr. so double check before you yeet it, bestie. 😭

---

✨ SEE ALSO ✨

the extended universe, no cap 🌈:

• Kernel file ./drivers/base/component.c
• overview(9)
• component_compare_of(9)
• component_release_of(9)
• component_compare_dev(9)
• component_compare_dev_name(9)
• component_match_add_release(9)
• component_match_add_typed(9)
• component_master_add_with_match(9)
• component_master_del(9)
• component_unbind_all(9)
• component_bind_all(9)
• component_add_typed(9)
• component_add(9)

---

k bye ily, this page came to you from ./drivers/base, dated October 2026 — stay hydrated, unbind responsibly, and remember: component_del(9) ate and left no crumbs 👑 💖