All of lore.kernel.org
 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: Wed, 22 Nov 2017 15:03:35 -0800	[thread overview]
Message-ID: <20171122230335.GA1228@nvidia.com> (raw)
In-Reply-To: <20171117145504.GA31760@infradead.org>

On Fri, Nov 17, 2017 at 06:55:04AM -0800, Christoph Hellwig wrote:
> On Wed, Nov 15, 2017 at 11:10:58AM -0800, Neo Jia wrote:
> > This will allow proprietary linux drivers to adopt SR-IOV spec from
> > PCI-SIG, also switch pci_reset_function to non-GPL symbol as it mainly
> > does pci config space access per spec.
> 
> Clear NAK.  Thos were added intentional, and even if they were changed
> your driver would still be a derived work and had to be published under
> a GPLv2-compatible license.

Hi Christoph,

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.

Similar interfaces we have seen inside Linux kernels are pci_enable_msi,
pci_enable_misx_range, which allows proprietary to work when following a PCI SIG
standard.

Thanks,
Neo

  reply	other threads:[~2017-11-22 23:03 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 [this message]
2017-11-23 13:23     ` Christoph Hellwig
2017-11-25  7:37       ` Neo Jia
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=20171122230335.GA1228@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.