linux-kernel - Re: [PATCH] regulator: dt-bindings: qcom,rpmh: Correct PM8550VE supplies

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: <173152002055.471967.17159431728276837850.b4-ty@kernel.org>
Date: Wed, 13 Nov 2024 17:47:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Bjorn Andersson <andersson@...nel.org>, 
 Abel Vesa <abel.vesa@...aro.org>, Trilok Soni <quic_tsoni@...cinc.com>, 
 Satya Durga Srinivasu Prabhala <quic_satyap@...cinc.com>, 
 Melody Olvera <quic_molvera@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH] regulator: dt-bindings: qcom,rpmh: Correct PM8550VE
 supplies

On Mon, 11 Nov 2024 16:35:44 -0800, Melody Olvera wrote:
> The PM8550VE has two more supplies (s1-8) than the PM8550VS (s1-6),
> so move to a correct if:then: clause to accurately reflect that.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: dt-bindings: qcom,rpmh: Correct PM8550VE supplies
      commit: 21ccadc64dae18bd092f1255bdbaf595f53381d5

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