From: David Vrabel <david.vrabel@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Campbell <ian.campbell@citrix.com>,
"open list:XEN NETWORK BACKEND DRIVER" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH 1/3] xen-netback: fix license ident used in MODULE_LICENSE
Date: Fri, 22 Jan 2016 13:14:24 +0000 [thread overview]
Message-ID: <56A22B30.3020206@citrix.com> (raw)
In-Reply-To: <1453466057-7176-2-git-send-email-wei.liu2@citrix.com>
On 22/01/16 12:34, Wei Liu wrote:
> The comment at the beginning of the file is the canonical source of
> licenses for this module. Currently it contains GPL and MIT license. Fix
> the code to reflect the reality.
"The MIT license" isn't really a thing. The closest is the X11
license[1], but this not applicable here either since the text in the
drivers does not refer to X11 trademarks etc.
You can either use "GPL" which would be correct for a Linux kernel
module since the alternate only applies when distributed separately from
Linux ("or, when distributed separately from the Linux kernel or
incorporated into other software packages, subject to the following
license:"); or you can use "GPL and additional rights".
(Or you could just leave it as-is since "Dual BSD/GPL" is close enough.)
David
[1] http://www.gnu.org/licenses/license-list.html#X11License
next prev parent reply other threads:[~2016-01-22 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453466057-7176-1-git-send-email-wei.liu2@citrix.com>
2016-01-22 12:34 ` [PATCH 1/3] xen-netback: fix license ident used in MODULE_LICENSE Wei Liu
2016-01-22 13:14 ` David Vrabel [this message]
2016-01-22 13:49 ` [Xen-devel] " Wei Liu
2016-01-22 14:15 ` Ian Campbell
2016-01-22 14:34 ` David Vrabel
2016-01-22 20:25 ` One Thousand Gnomes
2016-01-22 21:00 ` David Miller
2016-01-23 14:54 ` Wei Liu
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=56A22B30.3020206@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).