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 17:26:01 +0200 [thread overview]
Message-ID: <20130607172601.75b77122@skate> (raw)
In-Reply-To: <20130607144406.GS23859@titan.lakedaemon.net>
Dear Jason Cooper,
On Fri, 7 Jun 2013 10:44:06 -0400, Jason Cooper wrote:
> the patches in mvebu/fixes:
>
> 8eed481 arm: mvebu: fix the 'ranges' property to handle PCIe
> c6c003a ARM: mvebu: Fix ranges entry on XP GP board
> 00ed4a0 ARM: mvebu: Add a ranges entry to translate devbus childs
>
> added the ranges property for openblocks-ax3-4, and the gp, but nothing
> for the db. The patch
>
> b484ff4 ARM: mvebu: Add support for NOR flash device on Armada XP-DB board
>
> went into mvebu/dt because it was adding new capability.
>
> So the choices are to make mvebu/dt depend on mvebu/fixes because of
> your patch, or to split the patch because there is no real dependency
> between the two changes.
Ah, ok. That makes sense now. Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-07 15:26 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
2013-06-07 14:44 ` Jason Cooper
2013-06-07 15:26 ` Thomas Petazzoni [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=20130607172601.75b77122@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).