[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJnir+qA1Cgm5ATzsAH-pMqQSychLG=JQyUQg02dYb8TQ@mail.gmail.com>
Date: Tue, 31 May 2022 08:06:28 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Qun-Wei Lin <qun-wei.lin@...iatek.com>
Cc: Frank Rowand <frowand.list@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
devicetree@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<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 12:34 AM Qun-Wei Lin <qun-wei.lin@...iatek.com> 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__.
>
> Signed-off-by: Qun-Wei Lin <qun-wei.lin@...iatek.com>
> ---
> scripts/dtc/checks.c | 5 +++++
We don't take patches for dtc. You must send them to upstream dtc and
then it will be sync'ed to the kernel tree.
> 1 file changed, 5 insertions(+)
>
> diff --git a/scripts/dtc/checks.c b/scripts/dtc/checks.c
> index 781ba1129a8e..6ef4f2cd67b9 100644
> --- a/scripts/dtc/checks.c
> +++ b/scripts/dtc/checks.c
> @@ -325,6 +325,11 @@ static void check_node_name_chars_strict(struct check *c, struct dt_info *dti,
> {
> int n = strspn(node->name, c->data);
>
> + if (streq(node->name, "__overlay__")) {
> + /* HACK: Overlay fragments are a special case */
Not a hack IMO.
However, this should be checking for any node name starting with '__'.
Also, doesn't 'fragment@0' cause a warning about missing 'reg'?
Powered by blists - more mailing lists