devm_drm_put_bridge(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_drm_put_bridge(9) — the Kernel API Manual page, bestie edition ✨

okay so this is a page straight out of the Kernel API Manual, and honestly? It's a short one, but it's got lore. Sit down, hydrate, let's go 🫶

🌸 NAME 🌸

devm_drm_put_bridge — release a bridge reference that you got via devm, bestie. That's it, that's the job. ✨

🎀 SYNOPSIS 🎀

void devm_drm_put_bridge (struct device *dev , struct drm_bridge *bridge );

like… it takes two things and gives you back void. no notes, it's giving "I do one thing and I do it". 💅

🦋 ARGUMENTS 🦋

  • dev — the device that got the bridge via devm in the first place. yeah, that dev. it needs to be the one who did the getting, ok? 🙈
  • bridge — pointer to a struct drm_bridge that you obtained via devm. not a random bridge you found on the street, a devm one. 👑

💖 DESCRIPTION 💖

So this function does the same thing as drm_bridge_put, but specifically for bridge pointers that were obtained via devm functions — think things like devm_drm_bridge_alloc. same energy, devm flavour 🌈

Now for the part where I need you to listen, fr fr:

This function is a temporary workaround and MUST NOT be used. Manual handling of bridge lifetime is inherently unsafe. Not "unsafe if you're sloppy" unsafe — inherently unsafe. Like, it's in the description. Capital letters. Do not.

the way that "MUST NOT" is doing all the heavy lifting here 😭 please respect it. not me watching someone try to manually manage bridge lifetime… no ma'am, we don't do that here. 💀

🔥 SEE ALSO 🔥

the full friend group, in the order the manpage introduced them, because I'm not about to rearrange the group chat 💜

and that's the whole page, icon behaviour honestly ⭐

cute little sign-off: this one lives in ./drivers/gpu/drm (the Kernel API Manual corner of the world 🦋) and it's dated October 2026 — so yeah, future-coded. periodt. 💅🎀

📦 where this page comes from