regulator_ev...ard_notifier(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, this is regulator_event_forward_notifier(9) from the Kernel API Manual — the notifier callback for supply events 💖 she's niche, she's specific, and she's literally the main character of this page.

✨ SYNOPSIS ✨

int regulator_event_forward_notifier (struct notifier_block *nb ,
       unsigned long event , void *data );

🎀 ARGUMENTS 🎀

  • nb — the notifier block embedded in the regulator, iykyk 🫶
  • event — the regulator event code, aka the tea being passed along
  • data — unused; she's just there, lowkey chilling 🙈

💅 DESCRIPTION 💅

okay so the whole slay here is that she packages the event into a work item and schedules it in process context. She also takes a reference on rdev->dev to pin the regulator until the work completes — and yes bestie, you can see put_device doing its thing in the worker 😌. no cap, that reference is the whole point.

💖 RETURN 💖

  • NOTIFY_OK on success — slay ✨
  • NOTIFY_DONE for events that are not forwarded — she's not mad, she's just not passing those along 💅

🦋 SEE ALSO 🦋

Kernel file: ./drivers/regulator/core.c

😘 okay that's the whole page, bestie! it's serving regulator_event_forward_notifier(9) from the Kernel API Manual, sourced from ./drivers/regulator, and dated October 2026. slay, and remember: the vibe is forwarded, the facts are untouched 💅✨

📦 where this page comes from