devm_extcon...notifier_all(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 devm_extcon...notifier_all(9) 🎀

the Kernel API Manual, bestie edition 💅

okay so real talk, this page lives in the Kernel API Manual and it's about one very specific lil cleanup function. she's not flashy but she's literally essential, iykyk ✨

✨ NAME ✨

devm_extcon_unregister_notifier_all — that's her, that's the whole name, no extra subtitle, she said "my name is enough" 💁‍♀️

🦋 SYNOPSIS 🦋

void devm_extcon_unregister_notifier_all (struct device *dev , struct
extcon_dev *edev , struct notifier_block *nb );

she returns void (so like, nothing comes back, no gifts, no notes 😭) and she takes three args. periodt.

🌸 ARGUMENTS 🌸

  • dev — the device that owns the extcon device being created. like, the parent energy, the one holding the aux cord 🔌
  • edev — the extcon device itself. the main character, honestly 👑
  • nb — a notifier block to be registered. yes bestie, that's literally what the page says, don't come for me 🙈

💖 DESCRIPTION 💖

  • Resource-managed extcon_unregister_notifier_all

that's it, that's the description. one (1) bullet. she's lowkey minimalist and I respect it 🫶 the "resource-managed" part is doing heavy lifting here — the devm machinery handles the cleanup for you, no cap ⭐

🔥 SEE ALSO 🔥

the whole extcon devres friend group honestly, go say hi to all of them 💜

ngl the nb description says "to be registered" on an unregister page — that's what the original says, so I'm passing it straight to you, no edits, character for character 🙈✨

mwah, that's the page! 💅 this one comes from the ./drivers/extcon corner of the kernel, dated October 2026, and it goes by devm_extcon...notifier_all(9) — the title that got cut off in the corner but lives in our hearts forever 🎀🦋💖

📦 where this page comes from