From: Thomas Gleixner <tglx@linutronix.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: Jake Oshins <jakeo@microsoft.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [PATCH v9 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
Date: Sat, 19 Dec 2015 21:21:21 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1512192119060.28591@nanos> (raw)
In-Reply-To: <BY2PR0301MB1654386EBABB31E51CC6E55BA0E20@BY2PR0301MB1654.namprd03.prod.outlook.com>
On Sat, 19 Dec 2015, KY Srinivasan wrote:
> > From: Thomas Gleixner [mailto:tglx@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
next prev parent reply other threads:[~2015-12-19 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 22:54 jakeo
2015-12-09 22:54 ` [PATCH v9 1/7] drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num jakeo
2015-12-09 22:54 ` [PATCH v9 2/7] drivers:hv: Export hv_do_hypercall() jakeo
2015-12-09 22:54 ` [PATCH v9 3/7] PCI: Make it possible to implement a PCI MSI IRQ Domain in a module jakeo
2015-12-09 22:54 ` [PATCH v9 4/7] PCI: Add fwnode_handle to pci_sysdata jakeo
2016-01-08 21:57 ` Jake Oshins
2015-12-09 22:54 ` [PATCH v9 5/7] PCI: irqdomain: Look up IRQ domain by fwnode_handle jakeo
2015-12-09 22:54 ` [PATCH v9 6/7] drivers:hv: Define the channel type of Hyper-V PCI Express pass-through jakeo
2015-12-09 22:54 ` [PATCH v9 7/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-12-10 6:05 ` kbuild test robot
2015-12-10 7:24 ` kbuild test robot
2015-12-15 17:36 ` [PATCH v9 0/7] " KY Srinivasan
2015-12-19 11:27 ` Thomas Gleixner
2015-12-19 17:23 ` KY Srinivasan
2015-12-19 20:21 ` Thomas Gleixner [this message]
2015-12-20 5:03 ` KY Srinivasan
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=alpine.DEB.2.11.1512192119060.28591@nanos \
--to=tglx@linutronix.de \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jakeo@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®