On Sat, 19 Dec 2015, KY Srinivasan wrote:
> > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > On Tue, 15 Dec 2015, KY Srinivasan wrote:
> > >
> > > Of these 7 patches, Greg has committed all of the VMBUS
> > > related supporting patches (3 patches). Thomas, can you
> > > take the IRQ related patches through your tree.
> >
> > That does not make any sense.
> >
> > > > Jake Oshins (7):
> > > > drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
> > > > proc num
> > > > drivers:hv: Export hv_do_hypercall()
> > > > PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
> > > > PCI: Add fwnode_handle to pci_sysdata
> > > > PCI: irqdomain: Look up IRQ domain by fwnode_handle
> > > > drivers:hv: Define the channel type of Hyper-V PCI Express
> > > > pass-through
> > > > PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
> >
> > That series cannot be ripped apart. The PCI part does not even compile
> > w/o the drivers/hv part in place.
>
> What I was proposing was that after you pick up the hv related patches in
> Greg's tree in the next cycle, would you be willing to take the IRQ related
> patches through your tree. Sorry for the confusion.
You mean: PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
Right? Aside from the misleading subject line, I can pick that one
up. The rest wants to go through the PCI tree.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
