[PATCHv6 00/13] MSI support for Marvell EBU PCIe driver

Jason Cooper jason at lakedaemon.net
Wed Aug 7 11:51:24 EDT 2013


On Tue, Aug 06, 2013 at 02:08:18PM -0600, Stephen Warren wrote:
> 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.

I'll tag the head of mvebu/msi_common once it makes it through -next
successfully (I saw a linux-next email go by, but I haven't gotten that
far down my inbox yet)

Hopefully today or tomorrow, depending on where the -next problem is.
I'll send the PR along side that.  Once I tag it, you should be able to
base off of it before it gets into arm-soc, since the commit-id won't
change.

thx,

Jason.



More information about the linux-arm-kernel mailing list