From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: dts: imx28: Fix build warnings with W=1
Date: Sat, 5 Nov 2016 15:05:54 +0800 [thread overview]
Message-ID: <20161105070344.GB5597@dragon> (raw)
In-Reply-To: <CAOMZO5DbiHV-uR9bpdEFTfzDRXuWDao_RYxDCPJ1N=FuF4VCyQ@mail.gmail.com>
On Fri, Nov 04, 2016 at 06:51:06PM -0200, Fabio Estevam wrote:
> Hi Shawn,
>
> On Thu, Sep 8, 2016 at 11:03 AM, Shawn Guo <shawnguo@kernel.org> wrote:
> > On Mon, Sep 05, 2016 at 04:27:50PM -0300, Fabio Estevam wrote:
> >> diff --git a/arch/arm/boot/dts/imx28-tx28.dts b/arch/arm/boot/dts/imx28-tx28.dts
> >> index 0ebbc83..b4d4dbb 100644
> >> --- a/arch/arm/boot/dts/imx28-tx28.dts
> >> +++ b/arch/arm/boot/dts/imx28-tx28.dts
> >> @@ -35,7 +35,8 @@
> >> usbotg = &usb0;
> >> };
> >>
> >> - memory {
> >> + memory at 0 {
> >> + device_type = "memory";
> >> reg = <0 0>; /* will be filled in by U-Boot */
> >
> > I'm curious to know if the unit-address will be fixed up or not when
> > 'reg' property gets updated by U-Boot.
>
> Should I resend this series and keep imx28-tx28.dts unmodified?
Yeah, probably the best thing we can do.
Shawn
prev parent reply other threads:[~2016-11-05 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 19:27 [PATCH v2 1/4] ARM: dts: imx23: Remove skeleton.dtsi inclusion Fabio Estevam
2016-09-05 19:27 ` [PATCH v2 2/4] ARM: dts: imx28: " Fabio Estevam
2016-09-05 19:27 ` [PATCH v2 3/4] ARM: dts: imx23: Fix build warnings with W=1 Fabio Estevam
2016-09-12 20:09 ` Stefan Wahren
2016-09-05 19:27 ` [PATCH v2 4/4] ARM: dts: imx28: " Fabio Estevam
2016-09-08 14:03 ` Shawn Guo
2016-09-09 7:14 ` Lothar Waßmann
2016-09-12 12:09 ` Shawn Guo
2016-09-12 12:24 ` Javier Martinez Canillas
2016-11-04 20:51 ` Fabio Estevam
2016-11-05 7:05 ` 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=20161105070344.GB5597@dragon \
--to=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).