[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176070318151.57631.15443673679580823321.b4-ty@kernel.org>
Date: Fri, 17 Oct 2025 13:13:01 +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>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Jishnu Prakash <jishnu.prakash@....qualcomm.com>
Subject: Re: [PATCH v3 0/4] rpmh-regulators: Update rpmh-regulator driver
and dt-bindings for Glymur
On Thu, 18 Sep 2025 14:57:00 +0530, Kamal Wadhwa wrote:
> This series contains patches to update rpmh-regulator driver and
> dt-bindings for supporting the PMIC voltage regulators present on the
> boards with Qualcomm's next gen compute SoC - Glymur.
>
> Device tree changes aren't part of this series and will be posted
> separately after the official announcement of the Glymur SoC.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/4] dt-bindings: rpmh-regulator : Add compatibles for PMH01XX & PMCX0102
commit: 835dfb12fc389f36eb007657f163bd1c539dcd45
[2/4] dt-bindings: rpmh-regulator: Update pmic-id DT prop info for new CMD-DB
commit: 1356c98ef911e14ccfaf374800840ce5bdcb3bbd
[3/4] regulator: rpmh-regulator: Add support for new resource name format
commit: 6a8cdef7dc2a4c0dbde3f7d7100b3d99712a766b
[4/4] regulator: rpmh-regulator: Add RPMH regulator support for Glymur
commit: 65efe5404d151767653c7b7dd39bd2e7ad532c2d
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
Powered by blists - more mailing lists