linux-kernel - Re: [PATCH v2 1/1] regulator: core: forward undervoltage events downstream by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176054461213.193399.13443708649583416048.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 17:10:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Oleksij Rempel <o.rempel@...gutronix.de>
Cc: kernel@...gutronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/1] regulator: core: forward undervoltage events
 downstream by default

On Wed, 01 Oct 2025 12:56:49 +0200, Oleksij Rempel wrote:
> Forward critical supply events downstream so consumers can react in
> time.  An under-voltage event on an upstream rail may otherwise never
> reach end devices (e.g. eMMC).
> 
> Register a notifier on a regulator's supply when the supply is resolved,
> and forward only REGULATOR_EVENT_UNDER_VOLTAGE to the consumer's notifier
> chain. Event handling is deferred to process context via a workqueue; the
> consumer rdev is lifetime-pinned and the rdev lock is held while calling
> the notifier chain. The notifier is unregistered on regulator teardown.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: core: forward undervoltage events downstream by default
      commit: 433e294c3c5b5d2020085a0e36c1cb47b694690a

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark