From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: mvebu: fix ordering in Armada 370 .dtsi
Date: Fri, 14 Nov 2014 21:50:16 +0100 [thread overview]
Message-ID: <20141114205016.GJ2001@lunn.ch> (raw)
In-Reply-To: <20141114204333.GS27002@pengutronix.de>
On Fri, Nov 14, 2014 at 09:43:33PM +0100, Uwe Kleine-K?nig wrote:
> Commit a095b1c78a35 ("ARM: mvebu: sort DT nodes by address")
> missed placing the system-controller in the correct order.
>
> Fixes: a095b1c78a35 ("ARM: mvebu: sort DT nodes by address")
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> ---
> Hello Andrew,
>
> I guess your question concerning overlapping ranges doesn't stop this
> patch from being useful, does it?
Not at all.
Acked-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2014-11-14 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 19:36 [PATCH] ARM: mvebu: fix ordering in Armada 370 .dtsi Uwe Kleine-König
2014-11-14 20:22 ` Andrew Lunn
2014-11-17 9:49 ` Thomas Petazzoni
2014-11-14 20:43 ` [PATCH v2] " Uwe Kleine-König
2014-11-14 20:50 ` Andrew Lunn [this message]
2014-11-22 3:37 ` Jason Cooper
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=20141114205016.GJ2001@lunn.ch \
--to=andrew@lunn.ch \
--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).