From: Bjorn Andersson <andersson@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node
Date: Fri, 7 Apr 2023 09:34:42 -0700 [thread overview]
Message-ID: <20230407163442.ckbd4vxa5b2xu3eu@ripper> (raw)
In-Reply-To: <edb9fc8d-5d64-146f-fb82-6112c1d9455e@linaro.org>
On Mon, Mar 27, 2023 at 09:39:00PM +0200, Krzysztof Kozlowski wrote:
> On 27/03/2023 21:39, Bjorn Andersson wrote:
> > On Sun, Mar 26, 2023 at 11:16:05AM +0200, Krzysztof Kozlowski wrote:
> >> The soc node is supposed to have only device nodes with MMIO addresses,
> >> so move the DSI OPP out of it (it is used also by second DSI1 on
> >> SDM660):
> >>
> >
> > This node has been moved into the dsi node, so if we still want this,
> > could you please update the commit message.
>
> The OPP table has been moved *out of* DSI node. The v1 was moving
> inside, but this was not good approach, thus v2 moves it out.
>
> I don't understand what shall be updated here.
>
The commit message doesn't reflect what's in linux-next today and the
patch doesn't apply.
Regards,
Bjorn
next prev parent reply other threads:[~2023-04-07 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 9:16 [PATCH v2] arm64: dts: qcom: sdm630: move DSI opp-table out of soc node Krzysztof Kozlowski
2023-03-26 9:21 ` Dmitry Baryshkov
2023-03-26 9:22 ` Krzysztof Kozlowski
2023-03-26 10:03 ` Dmitry Baryshkov
2023-03-26 10:13 ` Krzysztof Kozlowski
2023-03-26 22:02 ` Dmitry Baryshkov
2023-03-27 17:48 ` Konrad Dybcio
2023-03-27 19:39 ` Bjorn Andersson
2023-03-27 19:39 ` Krzysztof Kozlowski
2023-04-07 16:34 ` Bjorn Andersson [this message]
2023-04-07 19:18 ` Krzysztof Kozlowski
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=20230407163442.ckbd4vxa5b2xu3eu@ripper \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).