From: Dmitry Torokhov <dtor@vmware.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: pv-drivers@vmware.com, Andy King <acking@vmware.com>,
vm-crosstalk@vmware.com, linux-kernel@vger.kernel.org,
George Zhang <georgezhang@vmware.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [Pv-drivers] [PATCH 04/10] VMCI: device driver implementaton.
Date: Thu, 25 Oct 2012 14:13:24 -0700 [thread overview]
Message-ID: <13812664.FoGKxWEYdK@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20121025210448.GB12352@kroah.com>
On Thursday, October 25, 2012 02:04:48 PM Greg KH wrote:
> On Thu, Oct 25, 2012 at 01:45:39PM -0700, Dmitry Torokhov wrote:
> > On Thursday, October 25, 2012 01:31:48 PM Greg KH wrote:
> > > On Thu, Oct 25, 2012 at 01:16:00PM -0700, Andy King wrote:
> > > > Hi Greg,
> > > >
> > > > > > +EXPORT_SYMBOL(vmci_device_get);
> > > > >
> > > > > EXPORT_SYMBOL_GPL() for this, and all other exports?
> > > >
> > > > We'd prefer to leave them as vanilla exports. While we're committed
> > > > to open-sourcing everything, including our non-upstreamed drivers,
> > > > we don't really have a strong opinion regarding consuming our exports
> > > > in closed-source (general GPL issues aside).
> > >
> > > You can't just say "general GPL issues aside". Honestly, given your
> > > company's prior actions in regards to Linux kernel drivers and the
> > > licenses of them, I don't trust them at all. To help gain that trust
> > > back, marking the exports in this manner will be a great improvement.
> > >
> > > To insist otherwise is to only reinforce my doubts, and reduce my
> > > wanting to even review or accept this code at all. Sorry about that.
> >
> > Huh? What are the concerns exactly? I do not really see difference between
> > EXPORT_SYMBOL() and EXPORT_SYMBOL_GPL(). The code either derivative of the
> > kernel or it is not and so it either falls under the kernel license or
> > not.
>
> I totally agree. In this case, do you think it falls under the kernel
> license or not?
VMCI implementation that we are submitting is GPL as witnessed by the license
notices on the source files ;)
>
> > From out perspective we do not really care what other code might use VMCI,
> > all our Linux drivers, even if not all are upstream [yet], are GPL.
>
> That's nice to hear, although without proof of that, we have to take
> your word :)
The source to Open VM Tools (which includes guest drivers that have not
been upstreamed yet) can be always found here:
https://sourceforge.net/projects/open-vm-tools/files/
and here:
git.opensource.vmware.com/opensource/open-vm-tools/
The hosted drivers are distributed in source form with the product and
here:
https://my.vmware.com/web/vmware/info/slug/desktop_end_user_computing/vmware_workstation/9_0#open_source
Thanks,
Dmitry
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2012-10-25 21:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 0:27 [PATCH 00/10] VMCI for Linux upstreaming George Zhang
2012-10-16 0:28 ` [PATCH 01/10] VMCI: context implementation George Zhang
2012-10-16 0:28 ` [PATCH 02/10] VMCI: datagram implementation George Zhang
2012-10-16 0:28 ` [PATCH 03/10] VMCI: doorbell implementation George Zhang
2012-10-16 0:28 ` [PATCH 04/10] VMCI: device driver implementaton George Zhang
2012-10-25 19:28 ` Greg KH
2012-10-25 20:16 ` [Pv-drivers] " Andy King
2012-10-25 20:31 ` Greg KH
2012-10-25 20:43 ` Bhavesh Davda
2012-10-25 21:03 ` Greg KH
2012-10-25 21:15 ` Dmitry Torokhov
2012-10-25 20:45 ` Dmitry Torokhov
2012-10-25 21:04 ` Greg KH
2012-10-25 21:13 ` Dmitry Torokhov [this message]
2012-10-25 21:18 ` Bhavesh Davda
2012-10-25 21:08 ` Andy King
2012-10-26 20:02 ` Andy King
2012-10-26 20:11 ` Greg KH
2012-10-16 0:28 ` [PATCH 05/10] VMCI: event handling implementation George Zhang
2012-10-16 0:29 ` [PATCH 06/10] VMCI: handle array implementation George Zhang
2012-10-16 0:29 ` [PATCH 07/10] VMCI: queue pairs implementation George Zhang
2012-10-16 0:29 ` [PATCH 08/10] VMCI: resource object implementation George Zhang
2012-10-16 0:29 ` [PATCH 09/10] VMCI: routing implementation George Zhang
2012-10-16 0:29 ` [PATCH 10/10] VMCI: Some header and config files George Zhang
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=13812664.FoGKxWEYdK@dtor-d630.eng.vmware.com \
--to=dtor@vmware.com \
--cc=acking@vmware.com \
--cc=georgezhang@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vm-crosstalk@vmware.com \
/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
Powered by JetHome