linux-kernel - Re: [PATCH] regulator: core: Propagate the regulator state in case of exclusive get

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]

Date: Tue, 12 Mar 2024 16:02:58 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Kory Maincent <kory.maincent@...tlin.com>
Cc: thomas.petazzoni@...tlin.com, Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: core: Propagate the regulator state in case
 of exclusive get

On Tue, 12 Mar 2024 10:16:38 +0100, Kory Maincent wrote:
> Previously, performing an exclusive get on an already-enabled regulator
> resulted in inconsistent state initialization between child and parent
> regulators. While the child's counts were updated, its parent's counters
> remained unaffected.
> 
> Consequently, attempting to disable an already-enabled exclusive regulator
> triggered unbalanced disables warnings from its parent regulator.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: Propagate the regulator state in case of exclusive get
      commit: e4ead3cdfd798092288f3a06b405cf98ded6fa10

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