From: Mark Brown <broonie@kernel.org>
To: linux-arm-msm@vger.kernel.org, Richard Acayan <mailingradian@gmail.com>
Cc: Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 0/2] RPMh Support for PM660 and PM660L
Date: Fri, 23 Sep 2022 18:21:37 +0100 [thread overview]
Message-ID: <166395369731.637366.12053156030098251858.b4-ty@kernel.org> (raw)
In-Reply-To: <20220920223331.150635-1-mailingradian@gmail.com>
On Tue, 20 Sep 2022 18:33:29 -0400, Richard Acayan wrote:
> Changes since v1:
> - properly label
>
> This patch series introduces support for the PM660 and PM660L on the RPMh
> mailbox. My initial Pixel 3a dts is not very minimal but I think that this
> series is trivial enough that it can be activated in a single commit.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] dt-bindings: regulator: qcom,rpmh: add pm660 and pm660l pmics
commit: 21c93a95553d0a07091ff9894f09f5bffbfd8c8a
[2/2] regulator: qcom-rpmh: add pm660 and pm660l pmics
commit: 911ce7cf72d9c1066a52928bffedaa103290db9e
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
prev parent reply other threads:[~2022-09-23 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 22:33 [PATCH v2 0/2] RPMh Support for PM660 and PM660L Richard Acayan
2022-09-20 22:33 ` [PATCH v2 1/2] dt-bindings: regulator: qcom,rpmh: add pm660 and pm660l pmics Richard Acayan
2022-09-21 7:38 ` Krzysztof Kozlowski
2022-09-23 13:14 ` Mark Brown
2022-09-20 22:33 ` [PATCH v2 2/2] regulator: qcom-rpmh: " Richard Acayan
2022-09-21 7:38 ` Krzysztof Kozlowski
2022-09-23 17:21 ` Mark Brown [this message]
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=166395369731.637366.12053156030098251858.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mailingradian@gmail.com \
--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