From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Jake Oshins <jakeo@microsoft.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
"olaf@aepfle.de" <olaf@aepfle.de>,
Mike Ebersol <Michael.Ebersol@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"apw@canonical.com" <apw@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs
Date: Fri, 12 Jun 2015 09:14:05 -0700 [thread overview]
Message-ID: <20150612161405.GA15911@kroah.com> (raw)
In-Reply-To: <DM2PR0301MB12323CC0C1132A7F71C79DD3ABBB0@DM2PR0301MB1232.namprd03.prod.outlook.com>
On Fri, Jun 12, 2015 at 03:11:14PM +0000, Jake Oshins wrote:
> This driver is intended to support both full PCI Express device pass through and also be the basis for SR-IOV networking on top of Hyper-V. These functions would allow somebody trying to make their NIC driver work on top of Hyper-V to exchange messages with their back-end Windows driver.
>
> My question is this. How does somebody delivering a platform usually work with the Linux community to deliver enablement code like this? I'm trying to work in the open, and go upstream early (or at least I think that understand what these things mean.) If the community doesn't want functions that have no callers (and I understand that, too) then how should I provide them to the NIC vendors?
You add the functions in a patch series along with the NIC driver that
uses it. We don't add functions with no callers, sorry.
hope this helps,
greg k-h
next prev parent reply other threads:[~2015-06-12 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 16:22 [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V jakeo
2015-06-11 16:22 ` [PATCH 1/6] drivers:hv: Modify vmbus to search for all MMIO ranges available jakeo
2015-06-11 16:22 ` [PATCH 2/6] drivers:hv: Move MMIO range picking from hyper_fb.mod to hv_vmbus.mod jakeo
2015-06-11 17:46 ` Greg KH
2015-06-11 16:22 ` [PATCH 3/6] arch:x86:hv: Add mechanism for Hyper-V paravirt drivers to hook msi message creation jakeo
2015-06-11 16:22 ` [PATCH 4/6] drivers:hv: Export a function that maps Linux proc num onto Hyper-V proc num jakeo
2015-06-11 16:22 ` [PATCH 5/6] drivers:hv: Define the channel type for Hyper-V PCI Express pass-through jakeo
2015-06-11 16:22 ` [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs jakeo
2015-06-11 17:46 ` Greg KH
2015-06-12 8:44 ` Paul Bolle
2015-06-12 15:11 ` Jake Oshins
2015-06-12 16:14 ` gregkh [this message]
2015-06-11 17:47 ` [PATCH 0/6] Front-end driver for PCIe Pass-through on Hyper-V Greg KH
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=20150612161405.GA15911@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Michael.Ebersol@microsoft.com \
--cc=apw@canonical.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jakeo@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=pebolle@tiscali.nl \
/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