From: Neil Armstrong <narmstrong@baylibre.com>
To: Anders Roxell <anders.roxell@linaro.org>,
robh+dt@kernel.org, khilman@baylibre.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: amlogic: meson-s4-aq222: fix waring for leading 0s
Date: Thu, 13 Jan 2022 11:39:47 +0100 [thread overview]
Message-ID: <e0a8be1b-025f-a599-0298-3521066860b0@baylibre.com> (raw)
In-Reply-To: <20220113102746.598763-1-anders.roxell@linaro.org>
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@00000000: 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@linaro.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@00000000 {
> + 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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-01-13 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:27 Anders Roxell
2022-01-13 10:39 ` Neil Armstrong [this message]
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=e0a8be1b-025f-a599-0298-3521066860b0@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=anders.roxell@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®