From: Shawn Guo <shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Marco Franchi <marco.franchi-3arQi8VN3Tc@public.gmane.org>
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWPLiZjB17Co1B2eb7JE58TQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
marcofrk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] ARM: dts: imx6qdl: Remove leading zeroes from unit addresses
Date: Fri, 13 Oct 2017 12:53:39 +0800 [thread overview]
Message-ID: <20171013045337.GF8833@dragon> (raw)
In-Reply-To: <1506017410-13263-1-git-send-email-marco.franchi-3arQi8VN3Tc@public.gmane.org>
On Thu, Sep 21, 2017 at 03:10:10PM -0300, Marco Franchi wrote:
> The following build warnings are seen with W=1:
>
> Warning (simple_bus_reg): Node /soc/sram@00900000 simple-bus unit
> address format error, expected "900000"
> Warning (simple_bus_reg): Node /soc/aips-bus@02000000 simple-bus unit
> address format error, expected "2000000"
> Warning (simple_bus_reg): Node /soc/aips-bus@02000000/pxp@020f0000
> simple-bus unit address format error, expected "20f0000"
> (...)
>
> Remove the leading zeroes from unit addresses to fix the warnings.
>
> Signed-off-by: Marco Franchi <marco.franchi-3arQi8VN3Tc@public.gmane.org>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-10-13 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 18:10 [PATCH] ARM: dts: imx6qdl: Remove leading zeroes from unit addresses Marco Franchi
[not found] ` <1506017410-13263-1-git-send-email-marco.franchi-3arQi8VN3Tc@public.gmane.org>
2017-09-22 13:45 ` Fabio Estevam
2017-10-13 4:53 ` Shawn Guo [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=20171013045337.GF8833@dragon \
--to=shawnguo-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWPLiZjB17Co1B2eb7JE58TQ@public.gmane.org \
--cc=marco.franchi-3arQi8VN3Tc@public.gmane.org \
--cc=marcofrk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).