From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/4] Add RPMh regulator support for PM7550 & PMR735B
Date: Mon, 14 Jul 2025 13:49:15 +0100 [thread overview]
Message-ID: <175249735528.52337.17952107558438792594.b4-ty@kernel.org> (raw)
In-Reply-To: <20250711-pm7550-pmr735b-rpmh-regs-v2-0-bca8cc15c199@fairphone.com>
On Fri, 11 Jul 2025 09:28:38 +0200, Luca Weiss wrote:
> Document and add support for the regulators on PM7550 and PMR735B, which
> can be paired with the Milos SoC.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/4] regulator: dt-bindings: qcom,rpmh: Add PM7550 compatible
commit: 729ff4a936c6f3faba78aaa8bc4291b6477c6576
[2/4] regulator: dt-bindings: qcom,rpmh: Add PMR735B compatible
commit: 20a01de0808364c26836cc8f47ed3b59a40a927d
[3/4] regulator: qcom-rpmh: add support for pmr735b regulators
commit: 28758434900ff4c4dce4e104fb5982ef3c0141ba
[4/4] regulator: qcom-rpmh: add support for pm7550 regulators
commit: 3aa47d2ec83316c24e1ed15a492b331802dc6a69
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:[~2025-07-14 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 7:28 [PATCH v2 0/4] Add RPMh regulator support for PM7550 & PMR735B Luca Weiss
2025-07-11 7:28 ` [PATCH v2 1/4] regulator: dt-bindings: qcom,rpmh: Add PM7550 compatible Luca Weiss
2025-07-11 7:28 ` [PATCH v2 2/4] regulator: dt-bindings: qcom,rpmh: Add PMR735B compatible Luca Weiss
2025-07-11 7:28 ` [PATCH v2 3/4] regulator: qcom-rpmh: add support for pmr735b regulators Luca Weiss
2025-07-11 7:28 ` [PATCH v2 4/4] regulator: qcom-rpmh: add support for pm7550 regulators Luca Weiss
2025-07-14 12:49 ` 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=175249735528.52337.17952107558438792594.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).