From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 00/10] MSI support for Marvell EBU PCIe driver
Date: Mon, 12 Aug 2013 13:54:51 -0400 [thread overview]
Message-ID: <20130812175451.GP25111@titan.lakedaemon.net> (raw)
In-Reply-To: <520920C1.5040904@wwwdotorg.org>
On Mon, Aug 12, 2013 at 11:52:01AM -0600, Stephen Warren wrote:
> On 08/12/2013 11:44 AM, Jason Cooper wrote:
> > On Mon, Aug 12, 2013 at 11:09:52AM -0600, Stephen Warren wrote:
> >> On 08/12/2013 10:37 AM, Jason Cooper wrote:
> >>> Thomas,
> >>>
> >>> Whole series applied as follows:
> >>>
> >>> +---+ mvebu/msi_pci (1-4,7)
> >>> |
> >>> +---+---+ mvebu/msi_irq (5,6)
> >>> |
> >>> +---+---+ mvebu/msi_mvebu (8-10)
> >>>
> >>> mvebu/msi_pci built successfully with Randy's config for x86_64.
> >>>
> >>> Thierry, I've tagged mvebu/msi_pci. Unless it all falls apart in -next,
> >>> those commit-id's won't change from what will be in arm-soc.
> >>
> >> So, the branch still isn't stable, hence I shouldn't use it as a
> >> baseline to apply Thierry's PCIe patches?
> >
> > It's as stable as I can make it. I've tested it for all known build
> > regressions (discovered in -next), and I see no reason to change it.
> > Anything needing fixed after today, I'll append the fix to it's HEAD if
> > appropriate.
>
> OK, if you will only append fixes rather than rebase the branch, then
> it's fine; what you said above implied that the commit IDs still might
> change.
Well, that's being generous. ;-) What I said was muddy as hell. Thanks
for making me clear that up.
> So, I'll try pulling this in with Thierry's patches today.
Great!
thx,
Jason.
prev parent reply other threads:[~2013-08-12 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 20:27 [PATCHv9 00/10] MSI support for Marvell EBU PCIe driver Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 01/10] PCI: use weak functions for MSI arch-specific functions Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 02/10] PCI: remove ARCH_SUPPORTS_MSI kconfig option Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 03/10] PCI: Introduce new MSI chip infrastructure Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 04/10] of: pci: add registry of MSI chips Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 05/10] irqchip: armada-370-xp: properly request resources Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 06/10] irqchip: armada-370-xp: implement MSI support Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 07/10] ARM: pci: add ->add_bus() and ->remove_bus() hooks to hw_pci Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 08/10] ARM: mvebu: the MPIC now provides MSI controller features Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 09/10] PCI: mvebu: add support for MSI Thomas Petazzoni
2013-08-09 20:27 ` [PATCHv9 10/10] ARM: mvebu: link PCIe controllers to the MSI controller Thomas Petazzoni
2013-08-12 16:37 ` [PATCHv9 00/10] MSI support for Marvell EBU PCIe driver Jason Cooper
2013-08-12 17:09 ` Stephen Warren
2013-08-12 17:44 ` Jason Cooper
2013-08-12 17:52 ` Stephen Warren
2013-08-12 17:54 ` Jason Cooper [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=20130812175451.GP25111@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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