linux-kernel - Re: [PATCH] regulator: Flag uncontrollable regulators as always

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: <164915112589.276837.9497597666608060283.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:32:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     broonie@...nel.org, lgirdwood@...il.com
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Flag uncontrollable regulators as always_on

On Fri, 25 Mar 2022 14:46:37 +0000, Mark Brown wrote:
> While we currently assume that regulators with no control available are
> just uncontionally enabled this isn't always as clearly displayed to
> users as is desirable, for example the code for disabling unused
> regulators will log that it is about to disable them. Clean this up a
> bit by setting always_on during constraint evaluation if we have no
> available mechanism for controlling the regualtor so things that check
> the constraint will do the right thing.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: Flag uncontrollable regulators as always_on
      commit: 261f06315cf7c3744731e36bfd8d4434949e3389

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