[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+vtq_rhkkyKo=ZntoLbe2vGxVvJ8Hx3xgHjT2GUKTDtQ@mail.gmail.com>
Date: Thu, 14 Dec 2017 13:04:11 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Mathieu Malaterre <malat@...ian.org>
Cc: Mark Rutland <mark.rutland@....com>,
Vineet Gupta <vgupta@...opsys.com>,
Alexey Brodkin <abrodkin@...opsys.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
arcml <linux-snps-arc@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arc: dts: Remove leading 0x and 0s from bindings notation
On Thu, Dec 14, 2017 at 10:53 AM, Mathieu Malaterre <malat@...ian.org> wrote:
> Improve the DTS files by removing all the leading "0x" and zeros to fix the
> following dtc warnings:
>
> Warning (unit_address_format): Node /XXX unit name should not have leading "0x"
>
> and
>
> Warning (unit_address_format): Node /XXX unit name should not have leading 0s
>
> Converted using the following command:
>
> find . -type f \( -iname *.dts -o -iname *.dtsi \) -exec sed -E -i -e "s/@0x([0-9a-fA-F\.]+)\s?\{/@\L\1 \{/g" -e "s/@0+([0-9a-fA-F\.]+)\s?\{/@\L\1 \{/g" {} +
>
> For simplicity, two sed expressions were used to solve each warnings separately.
>
> To make the regex expression more robust a few other issues were resolved,
> namely setting unit-address to lower case, and adding a whitespace before the
> the opening curly brace:
>
> https://elinux.org/Device_Tree_Linux#Linux_conventions
>
> This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from bindings notation")
>
> Reported-by: David Daney <ddaney@...iumnetworks.com>
> Suggested-by: Rob Herring <robh@...nel.org>
> Signed-off-by: Mathieu Malaterre <malat@...ian.org>
> ---
For the series,
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists