From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: arinc9.unal@gmail.com
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Paul Cercueil" <paul@crapouillou.net>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, erkin.bozoglu@xeront.com
Subject: Re: [PATCH 1/2] mips: dts: align LED node names with dtschema
Date: Tue, 14 Feb 2023 13:36:35 +0100 [thread overview]
Message-ID: <CAMhs-H9YCVe9AKQDv0DrdceFmV1SSOdM-twq65uNdj3+gE677A@mail.gmail.com> (raw)
In-Reply-To: <20230211104915.116253-1-arinc.unal@arinc9.com>
On Sat, Feb 11, 2023 at 11:50 AM <arinc9.unal@gmail.com> wrote:
>
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> The node names should be generic and DT schema expects certain pattern:
>
> mt7621-gnubee-gb-pc1.dtb: gpio-leds: 'power', 'system' do not match any of the regexes: '(^led-[0-9a-f]$|led)', 'pinctrl-[0-9]+'
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> .../dts/cavium-octeon/dlink_dsr-1000n.dts | 10 ++++-----
> .../boot/dts/cavium-octeon/dlink_dsr-500n.dts | 6 ++---
> arch/mips/boot/dts/ingenic/ci20.dts | 8 +++----
> arch/mips/boot/dts/pic32/pic32mzda_sk.dts | 6 ++---
> .../boot/dts/qca/ar9132_tl_wr1043nd_v1.dts | 8 +++----
> .../mips/boot/dts/qca/ar9331_dragino_ms14.dts | 8 +++----
> arch/mips/boot/dts/qca/ar9331_omega.dts | 2 +-
> arch/mips/boot/dts/qca/ar9331_tl_mr3020.dts | 8 +++----
> .../ralink/gardena_smart_gateway_mt7688.dts | 22 +++++++++----------
> .../boot/dts/ralink/mt7621-gnubee-gb-pc1.dts | 4 ++--
> .../boot/dts/ralink/mt7621-gnubee-gb-pc2.dts | 12 +++++-----
> 11 files changed, 47 insertions(+), 47 deletions(-)
Reviewed-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Thanks,
Sergio Paracuellos
next prev parent reply other threads:[~2023-02-14 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 10:49 [PATCH 1/2] mips: dts: align LED node names with dtschema arinc9.unal
2023-02-11 10:49 ` [PATCH 2/2] mips: dts: ralink: mt7621: add port@5 as CPU port arinc9.unal
2023-02-14 12:33 ` Sergio Paracuellos
2023-02-17 11:03 ` Thomas Bogendoerfer
2023-02-14 12:36 ` Sergio Paracuellos [this message]
2023-02-17 11:02 ` [PATCH 1/2] mips: dts: align LED node names with dtschema Thomas Bogendoerfer
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=CAMhs-H9YCVe9AKQDv0DrdceFmV1SSOdM-twq65uNdj3+gE677A@mail.gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=arinc9.unal@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).