From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Marvell PCIe driver improvements
Date: Wed, 22 May 2013 17:09:46 +0200 [thread overview]
Message-ID: <519CDFBA.8010607@free-electrons.com> (raw)
In-Reply-To: <20130522134319.GC31290@titan.lakedaemon.net>
On 05/22/2013 03:43 PM, Jason Cooper wrote:
> Thomas,
>
> On Wed, May 22, 2013 at 03:12:34PM +0200, Thomas Petazzoni wrote:
>> Bjorn, Jason, Andrew, Gregory,
>>
>> You'll find in this patch series 4 small patches that make various
>> improvements to the Marvell PCIe driver.
>>
>> I'd like those improvements to be kept separated from the original
>> PCIe driver itself: while the PCIe driver has been around and reviewed
>> for a long time, those improvements are newer. And I clearly do not
>> want the PCIe driver to miss 3.11 because of any problem that could be
>> found in those additional improvements.
>
> Agreed.
All the changes are located in one single file drivers/pci/host/pci-mvebu.c.
So as soon as they will be acked by Bjron, I think we can make a PR for them.
As nothing else depend of it, even if for a reason or another it is dropped,
there will be no reason to drop anything else.
>
> For Bjorn and others:
>
> The original patch series Thomas is referring to missed the merge window
> for v3.10 due to a build failure. It is currently sitting in our mvebu
> repo. The first three patches, "of/pci ..." are in mvebu/of_pci. The
> rest of the series is on top of that in the branch mvebu/pcie.
>
> I've sent pull requests for both branches to arm-soc. There are two
> other arm SoC pcie efforts which are depending on mvebu/of_pci. Hence
> why I did a separate branch.
>
> Both branches are also merged into mvebu/for-next, and have survived
> linux-next for three days or so. But, it's early, so we'll see how it
> goes. :-)
>
>> Bjorn, with your Acked-by, could the Marvell maintainers include those
>> patches in their branch, merged through arm-soc? They already have the
>> Marvell PCIe driver itself, so I believe it makes sense to merge those
>> improvements through the same path.
>
> I agree, please see above regarding arm-soc dependencies.
>
>> Jason, those patches have been prepared on top of my marvell-pcie-v10
>> branch, I hope that's ok for you. If you want me to rebase them on
>> some other branch in which you have integrated the PCIe driver, don't
>> hesitate to tell me to do so. That said, since those patches are only
>> touching the driver itself and no other file, they should not cause
>> any conflict with other changes.
>
> Should be fine, I'll let you know.
>
> thx,
>
> Jason.
>
--
Gregory Clement, 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-05-22 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 13:12 [PATCH 0/4] Marvell PCIe driver improvements Thomas Petazzoni
2013-05-22 13:12 ` [PATCH 1/4] pci: mvebu: no longer fake the slot location of downstream devices Thomas Petazzoni
2013-05-22 13:12 ` [PATCH 2/4] pci: mvebu: allow the enumeration of devices beyond physical bridges Thomas Petazzoni
2013-05-22 14:31 ` Bjorn Helgaas
2013-05-22 13:12 ` [PATCH 3/4] pci: mvebu: emulate an empty capability list Thomas Petazzoni
2013-05-22 14:39 ` Bjorn Helgaas
2013-05-22 14:55 ` Thomas Petazzoni
2013-05-22 13:12 ` [PATCH 4/4] pci: mvebu: fix the emulation of the status register Thomas Petazzoni
2013-05-22 14:49 ` Bjorn Helgaas
2013-05-22 13:43 ` [PATCH 0/4] Marvell PCIe driver improvements Jason Cooper
2013-05-22 15:09 ` Gregory CLEMENT [this message]
2013-05-22 15:18 ` Jason Cooper
2013-05-23 0:13 ` Willy Tarreau
2013-05-23 6:35 ` Thomas Petazzoni
2013-05-23 6:52 ` Willy Tarreau
2013-05-23 16:46 ` Jason Gunthorpe
2013-05-23 18:57 ` 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=519CDFBA.8010607@free-electrons.com \
--to=gregory.clement@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).