linux-kernel - Re: [RFT PATCH v2 1/2] regulator: core: Require regulator drivers to check uV for get_optimum

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:   Sun, 28 Aug 2022 22:03:56 +0100
From:   Mark Brown <broonie@...nel.org>
To:     dianders@...omium.org
Cc:     lgirdwood@...il.com, ahalaney@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: [RFT PATCH v2 1/2] regulator: core: Require regulator drivers to check uV for get_optimum_mode()

On Wed, 24 Aug 2022 14:22:56 -0700, Douglas Anderson wrote:
> The get_optimum_mode() for regulator drivers is passed the input
> voltage and output voltage as well as the current. This is because, in
> theory, the optimum mode can depend on all three things.
> 
> It turns out that for all regulator drivers in mainline only the
> current is looked at when implementing get_optimum_mode(). None of the
> drivers take the input or output voltage into account. Despite the
> fact that none of the drivers take the input or output voltage into
> account, though, the regulator framework will error out before calling
> into get_optimum_mode() if it doesn't know the input or output
> voltage.
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/2] regulator: core: Require regulator drivers to check uV for get_optimum_mode()
      commit: 55841199050d0c6c44eb7f24717816e6e372599f
[2/2] regulator: core: Don't err if allow-set-load but no allowed-modes
      commit: 57919f4a2ea47f75ac6117f7d99831f7fbd89bc7

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