linux-kernel - Re: [PATCH] arm64: dts: amlogic: meson-s4-aq222: fix waring for leading 0s

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 13 Jan 2022 11:39:47 +0100
From:   Neil Armstrong <narmstrong@...libre.com>
To:     Anders Roxell <anders.roxell@...aro.org>, robh+dt@...nel.org,
        khilman@...libre.com
Cc:     devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: meson-s4-aq222: fix waring for
 leading 0s

Hi,


On 13/01/2022 11:27, Anders Roxell wrote:
> When building allmodconfig the following waring shows up:
> 
> arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts:21.18-24.4: Warning (unit_address_format): /memory@...00000: unit name should not have leading 0s
> 
> Fixing the waring by dropping all the '0' except one.
> 
> Fixes: 1c1475389af0 ("arm64: dts: add support for S4 based Amlogic AQ222")
> Signed-off-by: Anders Roxell <anders.roxell@...aro.org>
> ---
>  arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts b/arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts
> index a942d7e06d6e..8ffbcb2b1ac5 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts
> +++ b/arch/arm64/boot/dts/amlogic/meson-s4-s805x2-aq222.dts
> @@ -18,7 +18,7 @@ aliases {
>  		serial0 = &uart_B;
>  	};
>  
> -	memory@...00000 {
> +	memory@0 {
>  		device_type = "memory";
>  		reg = <0x0 0x0 0x0 0x40000000>;
>  	};
> 


Thanks, I also noticed and fixed in the commit directly, it should be fixed on next -next

Neil