linux-kernel - Re: [PATCH 0/3] regulator: misc fixes

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: Windows password security audit tool. GUI, reports in PDF.

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

Date: Thu, 16 May 2024 16:58:08 +0100
From: Mark Brown <broonie@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 Matti Vaittinen <mazziesaccount@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] regulator: misc fixes

On Thu, 16 May 2024 11:52:44 +0300, Matti Vaittinen wrote:
> This series adds couple of a bit unrelated fixes/improvements which I
> implemented while working to support yet another ROHM PMIC.
> 
> Patch1 addresses a potential problem where the voltage selector for
> pickable-ranges is used in same fashion as a 'apply-bit'. Eg, when a
> regulator voltage is changed so that also the range changes, the effect
> of the range and voltage selector change is not taken into account until
> the voltage selector is written to hardware. In such case caching the
> voltage-selector value will cause the voltage range change to not change
> the actual output voltage.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: don't cache vsel to ensure voltage setting
      (no commit info)
[2/3] regulator: bd71828: Don't overwrite runtime voltages
      commit: 0f9f7c63c415e287cd57b5c98be61eb320dedcfc
[3/3] regulator: rohm-regulator: warn if unsupported voltage is set
      commit: cb3a0f84ae0caa5eabf40457485473edc1e2d3f0

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