From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Malaterre Subject: [PATCH 10/25] arm: orion5x: dts: Remove leading 0x and 0s from bindings notation Date: Fri, 15 Dec 2017 13:46:42 +0100 Message-ID: <20171215124642.30384-1-malat@debian.org> Return-path: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Mathieu Malaterre , Jason Cooper , Andrew Lunn , Sebastian Hesselbarth , Gregory Clement , Mark Rutland , Russell King , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org 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 -i -e "s/@\([0-9a-fA-FxX\.;:#]+\)\s*{/@\L\1 {/g" -e "s/@0x\(.*\) {/@\1 {/g" -e "s/@0+\(.*\) {/@\1 {/g" {} +^C 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 will solve as a side effect warning: Warning (simple_bus_reg): Node /XXX@ simple-bus unit address format error, expected "" This is a follow up to commit 4c9847b7375a ("dt-bindings: Remove leading 0x from bindings notation") Reported-by: David Daney Suggested-by: Rob Herring Signed-off-by: Mathieu Malaterre --- arch/arm/boot/dts/orion5x-linkstation.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/orion5x-linkstation.dtsi b/arch/arm/boot/dts/orion5x-linkstation.dtsi index e9991c83d7b7..7e418539fa54 100644 --- a/arch/arm/boot/dts/orion5x-linkstation.dtsi +++ b/arch/arm/boot/dts/orion5x-linkstation.dtsi @@ -126,7 +126,7 @@ read-only; }; - uboot_env@3F000 { + uboot_env@3f000 { reg = <0x3F000 0x1000>; }; }; -- 2.11.0