Re: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for Hyper-V VMs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel




[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux