From: David Woodhouse <dwmw2@infradead.org>
To: Neo Jia <cjia@nvidia.com>, 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: Sat, 25 Nov 2017 15:33:35 +0000 [thread overview]
Message-ID: <1511624015.32136.93.camel@infradead.org> (raw)
In-Reply-To: <20171125073751.GA28668@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Fri, 2017-11-24 at 23:37 -0800, Neo Jia wrote:
> 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.
Some, but not all. For example, the SVM interfaces are also exported
with EXPORT_SYMBOL_GPL, and may not be used by drivers which violate
the GPL licence of the kernel.
You have already been told that this won't be changed. Please stop asking.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
prev parent reply other threads:[~2017-11-25 15:33 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
2017-11-25 15:33 ` David Woodhouse [this message]
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=1511624015.32136.93.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=cjia@nvidia.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).