cpu_pm_unregister_notifier(9)
π cpu_pm_unregister_notifier β the Kernel API Manual page you actually wanna read π
okay so bestie, we're in the Kernel API Manual today and the star of the show is cpu_pm_unregister_notifier(9) β yes the whole entire name, she's long, she's iconic, deal with it β¨
πΈ NAME πΈ
cpu_pm_unregister_notifier β unregister a driver with cpu_pm π«Ά
β SYNOPSIS β
int cpu_pm_unregister_notifier (struct notifier_block *nb );
that's it. that's the whole vibe check. one function, one argument, she ate π
π¦ ARGUMENTS π¦
nbβ the notifier block to be unregistered, literally just hand her the block and she'll take it from there π
β¨ DESCRIPTION β¨
okay so here's the tea β β this function removes a driver from the CPU PM notifier list. like, she's the one who hits "leave group" on the notifier chain for you, no drama, no cap π
and the returns?? highkey important β this function has the same return conditions as raw_notifier_chain_unregister. so like, don't go inventing your own expectations, check that one for the full story, iykyk π
ngl bestie, "same return conditions as raw_notifier_chain_unregister" is doing a lot of heavy lifting here β that's the actual contract, so go look it up before you assume anything π
π SEE ALSO π
- Kernel file
./kernel/cpu_pm.c cpu_pm_register_notifier(9)β her counterpart, the "join group" one π«Άcpu_pm_enter(9)cpu_pm_exit(9)cpu_cluster_pm_enter(9)cpu_cluster_pm_exit(9)
like the whole cpu_pm friend group, fr fr π
and that's the page!! mwah π this one came to you from ./kernel, dated October 2026, and yes the header/footer both said cpu_pm_unregister_notifier(9) again because the manpage said it thrice and we respect the repetition π stay slaying, go unregister responsibly π§ββοΈπΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms