san_dgpu_not...r_unregister(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… san_dgpu_not...r_unregister(9) β€” Kernel API Manual πŸŽ€

okay bestie, welcome to the Kernel API Manual entry for san_dgpu_not...r_unregister(9). yes the title is long enough to need its own zip code, no we are not skipping it. let's get into it ✨


✨ NAME ✨

san_dgpu_notifier_unregister β€” unregister a SAN dGPU notifier. that's it, that's the whole vibe. you're taking the notifier back out of the registry, bestie, and honestly? iconic cleanup behaviour πŸ§ΉπŸ’–


🌸 SYNOPSIS 🌸

int san_dgpu_notifier_unregister (struct notifier_block *nb );

there she is. one function, one argument, returns an int. simple, clean, main character energy πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • nb β€” the notifier-block to unregister. like, the block. the one you're yeeting out of the notifier list. hand it over and the function knows exactly which one you mean 🫢

πŸ’œ SEE ALSO πŸ’œ

  • Kernel file ./drivers/platform/surface/surface_acpi_notify.c β€” go read the source, it's literally right there, iykyk πŸ“–
  • san_client_link(9)
  • san_dgpu_notifier_register(9) β€” yes, the opposite twin. you register, you unregister, balance is restored to the universe 🌈

ngl, if you're unregistering a notifier you didn't register, that's on you bestie 😭 the page doesn't say what happens, so don't come for me β€” just, like, be normal about it πŸ™ˆ

and that's the whole page, periodt πŸ’… this little gem lives under ./drivers/platform/surface, dated October 2026, from the Kernel API Manual β€” mwah, go touch some kernel code, ily, bye πŸŽ€β­πŸ’–

πŸ“¦ where this page comes from