From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dts: Remove leading 0x and 0s from bindings notation
Date: Fri, 15 Dec 2017 09:30:39 +0530 [thread overview]
Message-ID: <20171215040039.GB3322@vireshk-i7> (raw)
In-Reply-To: <20171214165350.27850-1-malat@debian.org>
On 14-12-17, 17:53, Mathieu Malaterre 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@caviumnetworks.com>
> Suggested-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> ---
> arch/arm/boot/dts/spear300.dtsi | 2 +-
> arch/arm/boot/dts/spear310.dtsi | 2 +-
> arch/arm/boot/dts/spear320.dtsi | 2 +-
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next parent reply other threads:[~2017-12-15 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171214165350.27850-1-malat@debian.org>
2017-12-15 4:00 ` Viresh Kumar [this message]
2017-12-15 8:50 ` [PATCH] arm: dts: Remove leading 0x and 0s from bindings notation Jesper Nilsson
2017-12-15 8:59 ` Krzysztof Kozlowski
2017-12-15 11:19 ` Mathieu Malaterre
2017-12-15 12:18 ` Mathieu Malaterre
2017-12-15 12:41 ` Krzysztof Kozlowski
[not found] ` <20171215111620.20379-1-malat@debian.org>
2017-12-15 11:16 ` [PATCH 25/25] arm: ste: " Mathieu Malaterre
[not found] ` <20171215111620.20379-5-malat@debian.org>
2017-12-26 4:17 ` [PATCH 05/25] arm: imx: " Shawn Guo
[not found] ` <20171215111620.20379-12-malat@debian.org>
2018-01-11 14:38 ` [PATCH 12/25] arm: socfpga: " Dinh Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171215040039.GB3322@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox