devm_lwmi_tm...ter_notifier(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 devm_lwmi_tm_unregister_notifier 🎀

okay bestie, so this is a page out of the Kernel API Manual and it's lowkey iconic — it's the devm-flavored cleanup twin of the thermal mode notifier stuff, and we're gonna walk through it together. no cap. 💅

✨ NAME ✨

devm_lwmi_tm_unregister_notifier — the girl whose whole job is removing a notifier from the blocking notifier chain. that's it, that's the vibe. 🦋

✨ SYNOPSIS ✨

void devm_lwmi_tm_unregister_notifier (void *data );

like, that's the whole signature. yes the spacing is a little feral, we don't fix it, we respect it. 🙈

✨ ARGUMENTS ✨

  • data — a void pointer to the notifier_block struct that gets registered. so it's the notifier block itself you're passing in, pointing at it, void-style. iykyk 🫶

✨ DESCRIPTION ✨

so what actually happens: this calls lwmi_tm_unregister_notifier to unregister the notifier block from the thermal mode notifier chain. boom. done. slay. 🔥

that's genuinely the whole plot — it's the cleanup baddie that takes your notifier block out of the chain so it stops getting called. main character energy of "you're done here bestie, go home." 👑

✨ RETURN ✨

  • 0 on success 💖
  • -ENOENT on error 😭

(yes, the synopsis says void — we report it exactly like the page does, we don't editorialize. ngl, the docs said what the docs said.) 💀

✨ SEE ALSO ✨

go read all of those too, they're literally the friend group of this function. 🌸

warning bestie: this is documentation of kernel API behaviour — stick to what the page says and don't go inventing semantics. if you're unregistering notifier blocks in real code, the register/unregister pairing is your bestie, not your enemy. 💜

and that's the whole page, no notes ✨ sourced from ./drivers/platform/x86/lenovo and dated October 2026 — like a little time capsule from the kernel, periodt. 🎀🦋💖

📦 where this page comes from