linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gnomes@lxorguk.ukuu.org.uk
Cc: ian.campbell@citrix.com, wei.liu2@citrix.com,
	david.vrabel@citrix.com, xen-devel@lists.xenproject.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	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:00:10 -0800 (PST)	[thread overview]
Message-ID: <20160122.130010.1969101813739677626.davem@davemloft.net> (raw)
In-Reply-To: <20160122202521.76b98494@lxorguk.ukuu.org.uk>

From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Date: Fri, 22 Jan 2016 20:25:21 +0000

>> The fact what include/linux/license.h:license_is_gpl_compatible includes
>> "Dual MIT/GPL" as an option seems to suggest that it is enough of a thing
>> to be validly used as the contents of a MODULE_LICENSE() thing.
> 
> Yes. The MIT licence most definitely exists, and people know what it
> means.
> 
> Also nobody should be changing the licence on anything unless they have
> the written permission of all rights holders on record, so it's best to
> leave it be 8)

+1

  reply	other threads:[~2016-01-22 21:00 UTC|newest]

Thread overview: 12+ 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   ` [Xen-devel] " David Vrabel
2016-01-22 13:49     ` 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 [this message]
2016-01-23 14:54           ` Wei Liu
2016-01-22 12:34 ` [PATCH 2/3] xen-blkback: " Wei Liu
2016-01-22 12:44   ` Roger Pau Monné
2016-01-22 12:34 ` [PATCH 3/3] xen-scsiback: " Wei Liu
2016-01-22 12:55   ` Juergen Gross

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=20160122.130010.1969101813739677626.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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).