drm_bridge_remove(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_bridge_remove(9)

okay so this is a page from the Kernel API Manual — yes bestie, the kernel has its own manual pages, we love a documented kernel 🫶 — and today's main character is drm_bridge_remove, which unregisters a bridge. Short page, iconic energy, let's go ✨

🌸 SYNOPSIS 🌸

void drm_bridge_remove (struct drm_bridge *bridge );

that's it. that's the whole function signature. void return, one argument, no drama 💅

🎀 ARGUMENTS 🎀

  • bridge — the bridge control structure. like, the actual struct we're about to yeet off the registry. she's the one getting removed, no cap.

✨ DESCRIPTION ✨

okay so what actually happens here 👀 — drm_bridge_remove takes the given bridge and removes it from the global list of registered bridges. the way that means nobody's gonna find it anymore: users looking it up via of_drm_find_and_get_bridge will come up empty, literally. she's off the grid. 🙈

but wait, she doesn't just vanish into the void — nope, the function also adds her to the lingering bridge list, which is exactly what it sounds like. it keeps track of the bridge until its allocated memory is eventually freed. so she's lingering, bestie. still on the books, just not on the guest list. 🦋

lowkey important: remove from registry ≠ freed. the lingering list is the whole point — memory cleanup comes later, not here. don't be out here assuming drm_bridge_remove frees anything 💀

🌈 SEE ALSO 🌈

a whole friend group, fr fr — go say hi:

and that's the page, bestie 🎀 this lil drop of kernel lore lives in ./drivers/gpu/drm, it's part of the Kernel API Manual, and it's dated October 2026 — so she's from the future, which honestly tracks 👑💜

📦 where this page comes from