[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161730974895.25526.12885475666064429104.b4-ty@kernel.org>
Date: Thu, 1 Apr 2021 21:43:17 +0100
From: Mark Brown <broonie@...nel.org>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Andy Gross <agross@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
satya priya <skakit@...eaurora.org>
Cc: Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
rnayak@...eaurora.org, Liam Girdwood <lgirdwood@...il.com>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
kgunda@...eaurora.org
Subject: Re: [PATCH V3 0/5] Add PM7325/PM8350C/PMR735A regulator support
On Wed, 31 Mar 2021 17:35:34 +0530, satya priya wrote:
> This series is dependent on below series which adds DT files for SC7280 SoC
> https://lore.kernel.org/patchwork/project/lkml/list/?series=488871
>
> satya priya (5):
> regulator: qcom-rpmh: Add pmic5_ftsmps520 buck
> regulator: qcom-rpmh: Add PM7325/PMR735A regulator support
> arm64: dts: qcom: sc7280: Add RPMh regulators for sc7280-idp
> dt-bindings: regulator: Convert RPMh regulator bindings to YAML
> dt-bindings: regulator: Add compatibles for PM7325/PMR735A
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/5] regulator: qcom-rpmh: Add pmic5_ftsmps520 buck
commit: 9405b4f7fa78b55fc83e5b5258f00e651aed5734
[2/5] regulator: qcom-rpmh: Add PM7325/PMR735A regulator support
commit: c4e5aa3dbee56bde70dfa03debc49bf9494fb3d9
[3/5] arm64: dts: qcom: sc7280: Add RPMh regulators for sc7280-idp
(no commit info)
[4/5] dt-bindings: regulator: Convert RPMh regulator bindings to YAML
commit: 7255f98d08c73f0bcf1397d3060fdb776d7aa147
[5/5] dt-bindings: regulator: Add compatibles for PM7325/PMR735A
commit: be724fd5b60dd083c8e39a4a2652e5017d2f7a20
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