linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neo Jia <cjia@nvidia.com>
To: Christoph Hellwig <hch@infradead.org>, <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <alex.williamson@redhat.com>,
	Kirti Wankhede <kwankhede@nvidia.com>
Subject: Re: [PATCH 1/1] Change pci_enable_sriov, pci_disable_sriov and pci_reset_function to non-GPL symbol.
Date: Fri, 24 Nov 2017 23:37:51 -0800	[thread overview]
Message-ID: <20171125073751.GA28668@nvidia.com> (raw)
In-Reply-To: <20171123132300.GA10736@infradead.org>

On Thu, Nov 23, 2017 at 05:23:00AM -0800, Christoph Hellwig wrote:
> > Just to be clear, here the request is to allow proprietary driver continue
> > supporting Linux OS when adopting SR-IOV - a PCIE virtualization technology
> > standardized by PCI SIG.
> 
> And the anser in the previous mail was pretty clear: no.  And while
> we're at it go talk to your lawyers again that you don't have a derived
> work, because I suspect you do with such intimate entangling.

Hi Christoph,

Right now, Linux kernel is providing PCI kernel interfaces to support
proprietary PCI driver when it follows the standard from PCI SIG spec. 

So here we are just following the precedence of such to enable a SR-IOV capable
device. I treat this no difference to the scenario when a proprietary PCI driver
is used to only support MSI (pci_enable_msi) and later add MSI-X support
(pci_enable_msix_range).

Thanks,
Neo

  reply	other threads:[~2017-11-25  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 19:10 [PATCH 1/1] Change pci_enable_sriov, pci_disable_sriov and pci_reset_function to non-GPL symbol Neo Jia
2017-11-17 14:55 ` Christoph Hellwig
2017-11-22 23:03   ` Neo Jia
2017-11-23 13:23     ` Christoph Hellwig
2017-11-25  7:37       ` Neo Jia [this message]
2017-11-25 15:33         ` David Woodhouse

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=20171125073751.GA28668@nvidia.com \
    --to=cjia@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=hch@infradead.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-pci@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).