From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: mvebu: ensure PCIe range is propagated in the .dts files
Date: Fri, 7 Jun 2013 10:32:41 +0200 [thread overview]
Message-ID: <20130607103241.3f82d71d@skate> (raw)
In-Reply-To: <20130606190321.GQ23859@titan.lakedaemon.net>
Dear Jason Cooper,
On Thu, 6 Jun 2013 15:03:21 -0400, Jason Cooper wrote:
> > Can you split this in to two patches, please:
> >
> > > arch/arm/boot/dts/armada-xp-db.dts | 1 +
> >
> > one for mvebu/dt
> >
> > > arch/arm/boot/dts/armada-xp-gp.dts | 5 +++--
> > > arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 5 +++--
> >
> > and one for mvebu/fixes?
>
> Nevermind, I've got a few minutes and would like to get it in for the
> last -next this week.
I must admit I don't quite get why the patch had to be split. The three
chunks do exactly the same thing for the three boards.
The only difference is that the part touching armada-xp-gp and
armada-xp-openblocks-ax3-4 was also adding some comments for each
range, while the one for armada-xp-db didn't had to do it because the
comments were already there.
So really, the armada-xp-db change is as much of a "fix" than the two
other changes.
To be honest, as long as they all go in 3.11, I'm fine, but I'm just
curious as to why it would have had to be split.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-07 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:21 [PATCH] Minor fix for jcooper/for-next Thomas Petazzoni
2013-06-06 9:21 ` [PATCH] arm: mvebu: ensure PCIe range is propagated in the .dts files Thomas Petazzoni
2013-06-06 18:11 ` Jason Cooper
2013-06-06 19:03 ` Jason Cooper
2013-06-07 8:32 ` Thomas Petazzoni [this message]
2013-06-07 14:44 ` Jason Cooper
2013-06-07 15:26 ` Thomas Petazzoni
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=20130607103241.3f82d71d@skate \
--to=thomas.petazzoni@free-electrons.com \
--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).