linux-kernel - Re: [PATCH v2 0/4] Add RPMh regulator support for PM7550 & PMR735B

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: <175249735528.52337.17952107558438792594.b4-ty@kernel.org>
Date: Mon, 14 Jul 2025 13:49:15 +0100
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>, 
 Luca Weiss <luca.weiss@...rphone.com>
Cc: ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org, Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Subject: Re: [PATCH v2 0/4] Add RPMh regulator support for PM7550 & PMR735B

On Fri, 11 Jul 2025 09:28:38 +0200, Luca Weiss wrote:
> Document and add support for the regulators on PM7550 and PMR735B, which
> can be paired with the Milos SoC.
> 
> 

Applied to

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

Thanks!

[1/4] regulator: dt-bindings: qcom,rpmh: Add PM7550 compatible
      commit: 729ff4a936c6f3faba78aaa8bc4291b6477c6576
[2/4] regulator: dt-bindings: qcom,rpmh: Add PMR735B compatible
      commit: 20a01de0808364c26836cc8f47ed3b59a40a927d
[3/4] regulator: qcom-rpmh: add support for pmr735b regulators
      commit: 28758434900ff4c4dce4e104fb5982ef3c0141ba
[4/4] regulator: qcom-rpmh: add support for pm7550 regulators
      commit: 3aa47d2ec83316c24e1ed15a492b331802dc6a69

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