From: Stephen Warren <swarren@wwwdotorg.org>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>,
Russell King <linux@arm.linux.org.uk>,
Maen Suleiman <maen@marvell.com>,
linux-pci@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
Gregory Clement <gregory.clement@free-electrons.com>,
Thierry Reding <thierry.reding@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv6 00/13] MSI support for Marvell EBU PCIe driver
Date: Tue, 06 Aug 2013 14:08:18 -0600 [thread overview]
Message-ID: <520157B2.8080205@wwwdotorg.org> (raw)
In-Reply-To: <20130806200256.GB19280@titan.lakedaemon.net>
On 08/06/2013 02:02 PM, Jason Cooper wrote:
> Thomas,
>
> In order to get some testing in -next, I've *tentatively* applied this
> series in the following way:
>
> +---+ mvebu/msi_common (1,2,3,10)
> |
> +---+---+ mvebu/msi_irq (4-9)
> |
> +---+---+ mvebu/msi_mvebu (11-13)
>
> I had to make one change to patch #9, I protected the last two blocks
> with #ifdef CONFIG_PCI_MSI to prevent a build failure at that point.
>
> mvebu/msi_common should be appropriate for Thierry to base off, however,
> I make no guarantees about the stability of the branch until I send a
> PR for it. Code-wise, it should be fine, but the commit-ids may change
> due to adding Tested-by's, etc.
When do you intend to send the pull-request? I need a stable branch
before I can even apply Thierry's changes, and I'd prefer to get those
changes applied and in linux-next well before I send my pull requests to
arm-soc. At the very latest, I need enough time to apply Thierry's
patches on top of your final version of that branch, get it briefly
tested, and then send a pull-request to arm-soc before -rc6 is out, so
if your pull request goes in just before -rc6, that's going to be a problem.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv6 00/13] MSI support for Marvell EBU PCIe driver
Date: Tue, 06 Aug 2013 14:08:18 -0600 [thread overview]
Message-ID: <520157B2.8080205@wwwdotorg.org> (raw)
In-Reply-To: <20130806200256.GB19280@titan.lakedaemon.net>
On 08/06/2013 02:02 PM, Jason Cooper wrote:
> Thomas,
>
> In order to get some testing in -next, I've *tentatively* applied this
> series in the following way:
>
> +---+ mvebu/msi_common (1,2,3,10)
> |
> +---+---+ mvebu/msi_irq (4-9)
> |
> +---+---+ mvebu/msi_mvebu (11-13)
>
> I had to make one change to patch #9, I protected the last two blocks
> with #ifdef CONFIG_PCI_MSI to prevent a build failure at that point.
>
> mvebu/msi_common should be appropriate for Thierry to base off, however,
> I make no guarantees about the stability of the branch until I send a
> PR for it. Code-wise, it should be fine, but the commit-ids may change
> due to adding Tested-by's, etc.
When do you intend to send the pull-request? I need a stable branch
before I can even apply Thierry's changes, and I'd prefer to get those
changes applied and in linux-next well before I send my pull requests to
arm-soc. At the very latest, I need enough time to apply Thierry's
patches on top of your final version of that branch, get it briefly
tested, and then send a pull-request to arm-soc before -rc6 is out, so
if your pull request goes in just before -rc6, that's going to be a problem.
next prev parent reply other threads:[~2013-08-06 20:08 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 13:25 [PATCHv6 00/13] MSI support for Marvell EBU PCIe driver Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 01/13] PCI: use weak functions for MSI arch-specific functions Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 02/13] PCI: remove ARCH_SUPPORTS_MSI kconfig option Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 16:48 ` Bjorn Helgaas
2013-08-01 16:48 ` Bjorn Helgaas
2013-08-01 16:48 ` Bjorn Helgaas
2013-08-01 13:25 ` [PATCHv6 03/13] PCI: Introduce new MSI chip infrastructure Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 04/13] irqdomain: add irq_alloc_mapping() function Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 05/13] irqdomain: refactor __irq_domain_add() Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 06/13] irqdomain: add support to associate an irq_domain with a msi_chip Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 07/13] irqdomain: add function to find a MSI irq_domain Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 08/13] irqchip: armada-370-xp: properly request resources Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 09/13] irqchip: armada-370-xp: implement MSI support Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 10/13] ARM: pci: add ->add_bus() and ->remove_bus() hooks to hw_pci Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 11/13] ARM: mvebu: the MPIC now provides MSI controller features Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 12/13] PCI: mvebu: add support for MSI Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 13:25 ` [PATCHv6 13/13] ARM: mvebu: link PCIe controllers to the MSI controller Thomas Petazzoni
2013-08-01 13:25 ` Thomas Petazzoni
2013-08-01 16:08 ` [PATCHv6 00/13] MSI support for Marvell EBU PCIe driver Stephen Warren
2013-08-01 16:08 ` Stephen Warren
2013-08-01 16:14 ` Thomas Petazzoni
2013-08-01 16:14 ` Thomas Petazzoni
2013-08-01 16:50 ` Bjorn Helgaas
2013-08-01 16:50 ` Bjorn Helgaas
2013-08-01 17:58 ` Thomas Petazzoni
2013-08-01 17:58 ` Thomas Petazzoni
2013-08-06 18:10 ` Thomas Petazzoni
2013-08-06 18:10 ` Thomas Petazzoni
2013-08-06 22:39 ` Benjamin Herrenschmidt
2013-08-06 22:39 ` Benjamin Herrenschmidt
2013-08-07 9:03 ` Thomas Petazzoni
2013-08-07 9:03 ` Thomas Petazzoni
2013-09-18 20:23 ` Grant Likely
2013-09-18 20:23 ` Grant Likely
2013-08-06 18:22 ` Daniel Price
2013-08-06 19:30 ` Jason Cooper
2013-08-06 20:02 ` Jason Cooper
2013-08-06 20:02 ` Jason Cooper
2013-08-06 20:08 ` Stephen Warren [this message]
2013-08-06 20:08 ` Stephen Warren
2013-08-07 15:51 ` Jason Cooper
2013-08-07 15:51 ` Jason Cooper
2013-08-07 6:59 ` Thierry Reding
2013-08-07 6:59 ` Thierry Reding
2013-08-07 15:55 ` Jason Cooper
2013-08-07 15:55 ` 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=520157B2.8080205@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=bhelgaas@google.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maen@marvell.com \
--cc=rob.herring@calxeda.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.