[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200902181613.mrffnxy4klc5l75d@akan>
Date: Wed, 2 Sep 2020 13:16:13 -0500
From: Nishanth Menon <nm@...com>
To: Suman Anna <s-anna@...com>
CC: Rob Herring <robh+dt@...nel.org>, Tero Kristo <t-kristo@...com>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Vignesh Raghavendra <vigneshr@...com>, <lokeshvutla@...com>,
<grygorii.strashko@...com>, <nsekhar@...com>
Subject: Re: [PATCH 7/7] arm64: dts: ti: k3-*: Fix up node_name_chars_strict
errors
On 11:54-20200902, Suman Anna wrote:
> On 9/1/20 5:30 PM, Nishanth Menon wrote:
> > Building with W=2 throws up a bunch of easy to fixup errors..
> > node_name_chars_strict is one of them.. Knock those out.
> >
> > Signed-off-by: Nishanth Menon <nm@...com>
> > ---
> > arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 6 +++---
> > arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 4 ++--
> > arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 16 ++++++++--------
> > .../dts/ti/k3-am654-industrial-thermal.dtsi | 12 ++++++------
> > .../boot/dts/ti/k3-j721e-common-proc-board.dts | 18 +++++++++---------
> > arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 6 +++---
> > .../arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 2 +-
> > arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 2 +-
> > 8 files changed, 33 insertions(+), 33 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
> > index 9c96e3f58c86..ff3e38408dbc 100644
> > --- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
> > @@ -305,7 +305,7 @@
> > no-1-8-v;
> > };
> >
> > - scm_conf: scm_conf@...000 {
> > + scm_conf: scm-conf@...000 {
> > compatible = "syscon", "simple-mfd";
> > reg = <0 0x00100000 0 0x1c000>;
> > #address-cells = <1>;
> > @@ -344,7 +344,7 @@
> > <0x4090 0x3>; /* SERDES1 lane select */
> > };
> >
> > - dss_oldi_io_ctrl: dss_oldi_io_ctrl@...0 {
> > + dss_oldi_io_ctrl: dss-oldi-io-ctrl@...0 {
> > compatible = "syscon";
> > reg = <0x0000041E0 0x14>;
>
> We should %s/41E0/41e0/, but that change is not directly associated with the
> patch subject line. Perhaps, an additional patch? Remember seeing similar
> warning on some downstream crypto nodes, but strangely I am not seeing on these
> upstream nodes.
yeah - probably a separate patch, but thanks, i can fix it as well(will
check if there are similar ones around as well).
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists