[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7c6f0015-cf50-4c8b-060d-f6641d0aeb16@gmail.com>
Date: Tue, 31 May 2022 20:45:30 -0500
From: Frank Rowand <frowand.list@...il.com>
To: Rob Herring <robh@...nel.org>
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 5/31/22 17:49, Rob Herring wrote:
> 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.
Yes, at least as of 5.18-rc1 the warning is only if
'-W node_name_chars_strict', so a dtbo -> dts pass will not give the
warning for node __overlay__ by default.
-Frank
>
> Rob
Powered by blists - more mailing lists