[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFyhxcvD+q7tp+-yrSFDKfR0mOHgyEAe=f_94aKLsOu0Og@mail.gmail.com>
Date: Tue, 9 Aug 2016 19:58:27 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Alan Cox <alan@...ux.intel.com>,
Greg KH <gregkh@...uxfoundation.org>, torvalds@...ux.intel.com,
Rusty Russell <rusty@...tcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ciaran.farrell@...e.com, christopher.denicolo@...e.com,
fontana@...rpeleven.org, copyleft-next@...ts.fedorahosted.org,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
"Theodore Ts'o" <tytso@....edu>, Paul Bolle <pebolle@...cali.nl>,
Peter Anvin <hpa@...or.com>, Joe Perches <joe@...ches.com>
Subject: Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2]
module.h: add copyleft-next >= 0.3.1 as GPL compatible)
On Tue, Aug 9, 2016 at 1:14 PM, Luis R. Rodriguez <mcgrof@...nel.org> wrote:
>
> I'm personally fine with MODULE_LICENSE("GPL") being used with copyleft-next code
> and find it sensible.
I'd rather have the kernel license be as clear as possible, so I'd
tend to prefer that
MODULE_LICENSE("GPL")
and then if you want to dual-license it, just put something like "or,
at your option, copyleft-next" in the comment at the top.
That makes it clear that as far as the kernel is concerned, it's
GPLv2, but if somebody finds it useful for other projects, they can
choose to take that file under copyleft-next (whatever version that
would be..).
Linus
Powered by blists - more mailing lists