From: Marijn Suijten <marijn.suijten@somainline.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
konrad.dybcio@somainline.org, agross@kernel.org,
angelogioacchino.delregno@somainline.org, rnayak@codeaurora.org,
jamipkettunen@somainline.org, krzysztof.kozlowski+dt@linaro.org,
martin.botka@somainline.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: (subset) [PATCH 1/2] dt-bindings: power: rpmpd: Add SM6375 power domains
Date: Sat, 17 Sep 2022 00:04:19 +0200 [thread overview]
Message-ID: <20220916220419.nk66b2ub634l6wsf@SoMainline.org> (raw)
In-Reply-To: <166321302060.788007.3857501388494145309.b4-ty@kernel.org>
On 2022-09-14 22:36:54, Bjorn Andersson wrote:
> On Sat, 16 Jul 2022 21:32:00 +0200, Konrad Dybcio wrote:
> > Add the bindings for SM6375 RPMPDs.
> >
> >
>
> Applied, thanks!
>
> [1/2] dt-bindings: power: rpmpd: Add SM6375 power domains
> commit: 2d48e6ea3080ef7b2424dabfb500e29b030129d6
It looks like my request [1] to move these rpmpd definitions from the
rpm*H*pd section of this file down to sit with the rest of the rpmpd
definitions hasn't made its way through?
> [2/2] soc: qcom: rpmpd: Add SM6375 support
> commit: df646a17f103c6f18ab85c5e3773763d18dc528b
[1]: https://lore.kernel.org/linux-arm-msm/20220721095946.wy3wbeib4ycwghzl@SoMainline.org/
- Marijn
prev parent reply other threads:[~2022-09-16 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 19:32 Konrad Dybcio
2022-07-16 19:32 ` [PATCH 2/2] soc: qcom: rpmpd: Add SM6375 support Konrad Dybcio
2022-07-20 22:28 ` [PATCH 1/2] dt-bindings: power: rpmpd: Add SM6375 power domains Rob Herring
2022-07-21 9:59 ` Marijn Suijten
2022-09-15 3:36 ` (subset) " Bjorn Andersson
2022-09-16 22:04 ` Marijn Suijten [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=20220916220419.nk66b2ub634l6wsf@SoMainline.org \
--to=marijn.suijten@somainline.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=devicetree@vger.kernel.org \
--cc=jamipkettunen@somainline.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.botka@somainline.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®