drmm_release_action(9)

✨ drmm_release_action(9) ✨

okay bestie, welcome to the Kernel API Manual 💖 this is a real page out of the kernel docs, and honestly? it's a little baddie. let's get into it 🎀

---

🌸 NAME 🌸

drmm_release_action — release a managed action from a &drm_device

like, you know how some things just wait around to be cleaned up later? yeah. this is the "ok actually do it right now" button 💅

---

✨ SYNOPSIS ✨

void drmm_release_action (struct drm_device *dev , drmres_release_t
action , void *data );

she's a void function, so she doesn't return anything — she just does the thing and dips 🦋

---

🎀 ARGUMENTS 🎀

• dev — the DRM device, aka the main character here 👑
• action — the function that would get called when dev is released
• data — an opaque pointer, passed along to action (she's mysterious, she's giving enigma, we don't look inside 🙈)

---

💖 DESCRIPTION 💖

so here's the tea, bestie: this function calls the action — the one that was previously added by drmm_add_action — immediately. right now. no waiting. no "later." periodt.

and because it's already been handled, the action is removed from the list of cleanup actions for dev. which means the way that it won't get called again in the final drm_dev_put — that's the whole point, that's the vibe check, that's the slay ✅

ngl this is a real lowkey important one: call it early, and the cleanup fires early. call it and it's gone from the list, so the final drm_dev_put won't double up on you 🔥

---

🫶 SEE ALSO 🫶

• Kernel file ./drivers/gpu/drm/drm_managed.c
• managed resources(9)
• drmm_kmalloc(9)
• drmm_kstrdup(9)
• drmm_kfree(9)

go read those too, they're literally the friend group 💜

---

k byeee, this page lives in ./drivers/gpu/drm and it's dated October 2026 — so mark your calendar, mwah 😭💅🌟