From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: efm32: remove skeleton.dtsi include and fix unit address warnings
Date: Mon, 5 Sep 2016 09:56:50 +0200 [thread overview]
Message-ID: <20160905075650.exmgxv6ulrbeqw45@pengutronix.de> (raw)
In-Reply-To: <20160830205250.15616-4-manabian@gmail.com>
On Tue, Aug 30, 2016 at 10:52:50PM +0200, Joachim Eastwood wrote:
> Removale of skeleton.dtsi allows us also to fix the following
> warning from the dts compiler:
> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name
>
> by adding proper unit addresses to the memory nodes. Also add missing
> device_type to the memory node while at it.
>
> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
> ---
> Hi Uwe,
>
> If you want I can take this through the lpc18xx tree. There doesn't seem
> too be many patches for efm32 lately (last one dates from 2014).
That's fine for me.
Acked-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2016-09-05 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 20:52 [PATCH 0/3] remove skeleton.dtsi from armv7-m.dtsi Joachim Eastwood
2016-08-30 20:52 ` [PATCH 1/3] ARM: dts: armv7-m: remove skeleton.dtsi include Joachim Eastwood
2016-08-30 22:14 ` Stefan Agner
2016-09-06 7:29 ` Alexandre Torgue
2016-09-05 19:01 ` Fwd: " Joachim Eastwood
2016-09-06 5:31 ` Uwe Kleine-König
2016-08-30 20:52 ` [PATCH 2/3] ARM: dts: lpc18xx: remove skeleton.dtsi include and fix unit address warnings Joachim Eastwood
2016-08-30 20:52 ` [PATCH 3/3] ARM: dts: efm32: " Joachim Eastwood
2016-09-05 7:56 ` Uwe Kleine-König [this message]
2016-09-05 18:56 ` Joachim Eastwood
2016-08-30 22:14 ` [PATCH 0/3] remove skeleton.dtsi from armv7-m.dtsi Rob Herring
2016-08-31 8:19 ` Vladimir Murzin
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=20160905075650.exmgxv6ulrbeqw45@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).