linux-kernel - Re: [PATCH 0/2] Add rpmh regulator support for Kaanapali

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: <176123658056.145979.6028101761014548543.b4-ty@kernel.org>
Date: Thu, 23 Oct 2025 17:23:00 +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>, 
 Jingyi Wang <jingyi.wang@....qualcomm.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org, aiqun.yu@....qualcomm.com, 
 tingwei.zhang@....qualcomm.com, trilok.soni@....qualcomm.com, 
 yijie.yang@....qualcomm.com, 
 Jishnu Prakash <jishnu.prakash@....qualcomm.com>
Subject: Re: [PATCH 0/2] Add rpmh regulator support for Kaanapali

On Wed, 24 Sep 2025 16:30:46 -0700, Jingyi Wang wrote:
> Add rpmh regulator support for Kaanapali by adding PMR735D PMIC.
> 
> dependency:
> https://lore.kernel.org/all/20250916-glymur-rpmh-regulator-driver-v2-0-c6593ff9b4be@oss.qualcomm.com/#t
> 
> 

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: qcom,rpmh: Add support for PMR735D
      commit: f76dbe127f1b5910e37dfe307d2de5c13d61ed89
[2/2] regulator: rpmh-regulator: Add RPMH regulator support for PMR735D
      commit: d054cc3a2ccfb19484f3b54d69b6e416832dc8f4

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