lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 12 Jun 2015 09:14:05 -0700
From:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:	Jake Oshins <jakeo@...rosoft.com>
Cc:	Paul Bolle <pebolle@...cali.nl>, "olaf@...fle.de" <olaf@...fle.de>,
	Mike Ebersol <Michael.Ebersol@...rosoft.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"apw@...onical.com" <apw@...onical.com>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
Subject: Re: [PATCH 6/6] drivers:pci:hv: New paravirtual PCI front-end for
 Hyper-V VMs

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ