From: Mark Brown <broonie@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: (subset) [PATCH 0/3] arm64: qcom: add PMIC regulators for sa8775p
Date: Thu, 06 Apr 2023 22:31:04 +0100 [thread overview]
Message-ID: <168081666418.315518.2405515023822683417.b4-ty@kernel.org> (raw)
In-Reply-To: <20230406192811.460888-1-brgl@bgdev.pl>
On Thu, 06 Apr 2023 21:28:08 +0200, Bartosz Golaszewski wrote:
> Here are the remaining patches from the big PMIC series that add the DT
> bindings for RPMH regulators for SA8775P platforms, implement relevant
> support in the driver and add the regulator nodes to the sa8775p-ride
> board .dts.
>
> Since the first submission:
> - the DT bindings now contain the missing supply properties
> - the ldo8 min voltage has been increased
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/3] dt-bindings: regulator: qcom,rpmh: add compatible for pmm8654au RPMH
commit: ba0887a6b94ea7f77df1e464aeca45758b4d92c3
[2/3] regulator: qcom-rpmh: add support for pmm8654au regulators
commit: 65f1b1dc0cc90236ed9be3970f4a763e853f3aab
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
next prev parent reply other threads:[~2023-04-06 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 19:28 [PATCH 0/3] arm64: qcom: add PMIC regulators for sa8775p Bartosz Golaszewski
2023-04-06 19:28 ` [PATCH 1/3] dt-bindings: regulator: qcom,rpmh: add compatible for pmm8654au RPMH Bartosz Golaszewski
2023-04-07 8:43 ` Krzysztof Kozlowski
2023-04-06 19:28 ` [PATCH 2/3] regulator: qcom-rpmh: add support for pmm8654au regulators Bartosz Golaszewski
2023-04-06 19:28 ` [PATCH 3/3] arm64: dts: qcom: sa8775p-ride: add PMIC regulators Bartosz Golaszewski
2023-04-06 20:36 ` Konrad Dybcio
2023-04-06 21:31 ` Mark Brown [this message]
2023-04-07 18:36 ` (subset) [PATCH 0/3] arm64: qcom: add PMIC regulators for sa8775p Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168081666418.315518.2405515023822683417.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox