linux-kernel - Re: [PATCH 0/2] regulator: rk808: fix regulator ranges on RK806

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]

Message-Id: <170958389453.755725.8219793459949047424.b4-ty@kernel.org>
Date: Mon, 04 Mar 2024 20:24:54 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Matti Vaittinen <mazziesaccount@...il.com>, 
 shengfei Xu <xsf@...k-chips.com>, 
 Sebastian Reichel <sebastian.reichel@...labora.com>, 
 Quentin Schulz <foss+kernel@...il.net>
Cc: linux-kernel@...r.kernel.org, 
 Quentin Schulz <quentin.schulz@...obroma-systems.com>
Subject: Re: [PATCH 0/2] regulator: rk808: fix regulator ranges on RK806

On Fri, 23 Feb 2024 14:11:21 +0100, Quentin Schulz wrote:
> The regulator ranges aren't really matching what they should be for the
> buck and ldo regulators on RK806. They are not wrong per-se but they are
> a bit misleading.
> 
> The only change in behavior expected is that the buck regulators
> shouldn't be able to say that 3.65V is possible.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: rk808: fix buck range on RK806
      commit: 5803b54068435be3a3254f9ecdc1ebd5c18718a8
[2/2] regulator: rk808: fix LDO range on RK806
      commit: 6717ff5533f332ef7294655629b8fa5fb8b132de

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