[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220531214914.GA2388344-robh@kernel.org>
Date: Tue, 31 May 2022 16:49:14 -0500
From: Rob Herring <robh@...nel.org>
To: Frank Rowand <frowand.list@...il.com>
Cc: Qun-Wei Lin <qun-wei.lin@...iatek.com>, matthias.bgg@...il.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, casper.li@...iatek.com,
chinwen.chang@...iatek.com, kuan-ying.lee@...iatek.com
Subject: Re: [PATCH] scripts: dtc: fix a false alarm for
node_name_chars_strict
On Tue, May 31, 2022 at 04:43:18PM -0400, Frank Rowand wrote:
> On 5/31/22 01:33, Qun-Wei Lin wrote:
> > The function check_node_name_chars_strict issues a false alarm when
> > compiling an overlay dts.
> >
> > /fragment@..._overlay__: Character '_' not recommended in node name
> >
> > This workaround will fix it by skip checking for node named __overlay__.
>
> This is not a false alarm.
>
> Do not special case node name "__overlay__". This node name should never
> occur in a modern overlay source file.
A dtbo -> dts pass will give warnings, so handling these nodes is
worthwhile. Though thinking a bit more about it, I think this one is off
by default, but W=2 turns it on.
Rob
Powered by blists - more mailing lists