mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@linux.intel.com>,
	linux-kernel@vger.kernel.org, joe@perches.com,
	pebolle@tiscali.nl, gnomes@lxorguk.ukuu.org.uk,
	christopher.denicolo@suse.com, hpa@zytor.com,
	Rusty Russell <rusty@rustcorp.com.au>,
	Greg KH <gregkh@linuxfoundation.org>,
	"Luis R. Rodriguez" <mcgrof@kernel.org>,
	ciaran.farrell@suse.com,
	Discussion and development of copyleft-next 
	<copyleft-next@lists.fedorahosted.org>
Subject: Re: [copyleft-next] Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)
Date: Wed, 10 Aug 2016 03:25:30 +0200	[thread overview]
Message-ID: <20160810012530.GI3296@wotan.suse.de> (raw)
In-Reply-To: <20160809201448.GE3296@wotan.suse.de>

On Tue, Aug 09, 2016 at 10:14:48PM +0200, Luis R. Rodriguez wrote:
> On Tue, Aug 09, 2016 at 09:04:35PM +0100, Alan Cox wrote:
> > > > (Going back to pick up the specific licence thread)
> > 
> > > > 
> > > > I'd like to see Richard do so as well.
> > > With Richard that's 3 attorneys now.
> > 
> > None of whom I believe represent the Linux project or foundation ?
> > 
> > Linus has to make this call, nobody else and he is probablygoing to go
> > ape if you try and sneak another licence into the kernel without
> > flagging it up with him clearly first. You need to discuss it with
> > Linus up front.
> 
> To be clear I first poked the Linux Foundation about this, I went through the
> process recommended by them. If there is a process out of place its by no
> means an issue on my end.
> 
> > > I'll proceed to submit some code with this license as you request,
> > > Rusty.  Its
> > > however not for modules yet so I would not make use of the
> > > MODULE_LICENSE("copyleft-next") tag yet, however the license will be
> > > on top of
> > > a header.
> > 
> > We have the GPL/extra rights tag for this already. Also when it's
> > merged with the kernel we'd I'm sure pick the derivative work under the
> > GPL option so we'd only need the GPL tag.
> > 
> > There are specific reasons for the extra rights language - it avoids
> > games like MODULE_LICENSE("BSD") and then giving people just a binary
> > and it being counted as GPL compliant activity. The same problem exists
> > in your licence post sunset. That single tag is also why we don't have
> > to list BSD, MIT, and every variant thereof in the table which saves us
> > so much pain. If you must have the actual text in the .ko file then put
> > it in your MODULE_DESCRIPTION().
> 
> I'm personally fine with MODULE_LICENSE("GPL") being used with copyleft-next code
> and find it sensible.

Adding Linus now, for some reason I think you added him with an incorrect
domain name, Alan.

  Luis

  reply	other threads:[~2016-08-10  1:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 18:35 [PATCH] module.h: add copyleft-next >= 0.3.1 as GPL compatible Luis R. Rodriguez
2016-06-29 19:05 ` Luis R. Rodriguez
2016-06-29 19:46   ` Greg KH
2016-06-29 20:03     ` Luis R. Rodriguez
2016-06-29 20:13     ` H. Peter Anvin
2016-06-29 21:43   ` Paul Bolle
2016-06-29 22:01     ` Luis R. Rodriguez
2016-06-29 22:45       ` Paul Bolle
2016-06-29 23:01         ` Luis R. Rodriguez
2016-06-29 23:22           ` Paul Bolle
2016-06-29 23:29             ` Luis R. Rodriguez
2016-06-29 20:49 ` Paul Bolle
2016-06-30 22:50   ` Luis R. Rodriguez
2016-06-30 22:53 ` [PATCH v2] " Luis R. Rodriguez
2016-07-01 15:42   ` Greg KH
2016-07-18  3:26     ` Rusty Russell
2016-07-19 22:38       ` Greg KH
2016-07-19 23:29         ` Richard Fontana
2016-07-21  6:04         ` Rusty Russell
2016-07-22  0:07         ` Luis R. Rodriguez
2016-08-09 20:04           ` Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible) Alan Cox
2016-08-09 20:14             ` Luis R. Rodriguez
2016-08-10  1:25               ` Luis R. Rodriguez [this message]
2016-08-10  2:58               ` Linus Torvalds
2017-05-11 18:02                 ` Luis R. Rodriguez
2017-05-15 15:18                   ` Alan Cox
2017-05-16 23:27                     ` Luis R. Rodriguez
2017-05-17 13:36                       ` Alan Cox
2017-05-17 16:55                       ` Theodore Ts'o
2017-05-17 17:41                         ` [copyleft-next] " Luis R. Rodriguez
2017-05-18 22:12                           ` Theodore Ts'o
2017-05-18 23:04                             ` Luis R. Rodriguez
2017-05-18 23:08                               ` David Lang
2017-05-18 23:29                                 ` Luis R. Rodriguez
2017-05-19 15:15                                   ` Theodore Ts'o
2017-05-19 11:31                               ` Alan Cox
2017-05-19 15:09                                 ` Luis R. Rodriguez
2017-05-19 17:59                                   ` Luis R. Rodriguez
2017-05-19 18:04                                     ` Luis R. Rodriguez
2017-05-19 22:55                                       ` Alan Cox
2017-05-25 17:05                                       ` Pavel Machek
2017-05-25 17:31                                         ` Luis R. Rodriguez
2017-05-25 20:14                                           ` Pavel Machek
2017-05-25 22:54                                             ` Luis R. Rodriguez
2016-08-09 21:46             ` Richard Fontana

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=20160810012530.GI3296@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=alan@linux.intel.com \
    --cc=christopher.denicolo@suse.com \
    --cc=ciaran.farrell@suse.com \
    --cc=copyleft-next@lists.fedorahosted.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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

Powered by JetHome