From: Matthias Brugger <matthias.bgg@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: mediatek: align operating-points table name with dtschema
Date: Tue, 19 Apr 2022 16:31:59 +0200 [thread overview]
Message-ID: <448093df-288f-3c49-270e-5d830a986b27@gmail.com> (raw)
In-Reply-To: <165036314214.180327.9860190048104061653.b4-ty@linaro.org>
On 19/04/2022 12:12, Krzysztof Kozlowski wrote:
> On Fri, 20 Aug 2021 10:16:15 +0200, Krzysztof Kozlowski wrote:
>> Align the name of operating-points node to dtschema to fix warnings like:
>>
>> arch/arm64/boot/dts/mediatek/mt8173-elm.dt.yaml:
>> opp_table0: $nodename:0: 'opp_table0' does not match '^opp-table(-[a-z0-9]+)?$'
>>
>>
>
> Applied, thanks!
Could you please provide a stable branch for this patches? So that I can pull
that into my branch. This will help to reduce merge conflicts later on.
Thanks,
Matthias
>
> [1/2] arm64: dts: mediatek: align operating-points table name with dtschema
> commit: c743bb394d35b782ae9d9ab815d6053500914533
> [2/2] arm64: dts: mediatek: align thermal zone node names with dtschema
> commit: 54ff423f837db59db0626a00d091e45dcc46787e
>
> Best regards,
next prev parent reply other threads:[~2022-04-19 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 8:16 [PATCH 1/2] arm64: dts: mediatek: align operating-points table name with dtschema Krzysztof Kozlowski
2021-08-20 8:16 ` [PATCH 2/2] arm64: dts: mediatek: align thermal zone node names " Krzysztof Kozlowski
2022-04-19 10:12 ` [PATCH 1/2] arm64: dts: mediatek: align operating-points table name " Krzysztof Kozlowski
2022-04-19 14:31 ` Matthias Brugger [this message]
2022-04-19 14:34 ` Krzysztof Kozlowski
2022-04-19 14:50 ` Matthias Brugger
2022-04-07 20:34 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=448093df-288f-3c49-270e-5d830a986b27@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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).