From: "Ted Ts'o" <tytso@mit.edu>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
Keith Packard <keithp@keithp.com>,
Ralf Baechle <ralf@linux-mips.org>,
David Woodhouse <dwmw2@infradead.org>,
Stephen Hemminger <shemminger@vyatta.com>,
"John W. Linville" <linville@tuxdriver.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK
Date: Fri, 6 Apr 2012 22:49:41 -0400 [thread overview]
Message-ID: <20120407024941.GB11295@thunk.org> (raw)
In-Reply-To: <CAB=NE6Xt3yeCvW-t7mbEWoYr04Rg1uvObAMTatAdpHtgsdZvYA@mail.gmail.com>
On Fri, Apr 06, 2012 at 05:51:51PM -0700, Luis R. Rodriguez wrote:
>
> Its a good point that we are not declaring the exact license used for
> software, and while that is useful the "Dual BSD/GPL" tag is
> misleading. As I see it there are four options:
So the real question is what is the purpose of MODULE_LICENSE()?
Specifically, is it intended for anything other than to tell the that
this module is OK to use EXPORT_SYMBOL_GPL symbols?
Your patch which changes things like
MODULE_LICENSE("Dual BSD/GPL");
to
MODULE_LICENSE("GPL-Compatible");
in my opinion, muddles things even more, since now in some cases
MODULE_LICENSE() will name a specific license (i.e., GPL), and in
other cases, a set of licenses (i.e., GPL-Compatible). After all,
isn't a GPL license by definition GPL-compatible? So why not change
*all* MODULE_LICENSE(GPL) statements to be
MODULE_LICENSE(GPL-Compatible)? If that seems like a large, pointless
patch, then maybe it's not worth it to change "Dual BSD/GPL" to
"GPL-Compatible".
I also really don't see how this helps License compliance folks. If
the BSD folks trying to figure out whether or not they can use some
piece of code, "GPL-Compatible" is no more useful than as "Dual
BSD/GPL". In fact, Dual BSD/GPL might actually be more useful since
at least to me it says it can be used under the BSD or GPL license,
which is precisely what the BSD folks need.
Regards,
- Ted
next prev parent reply other threads:[~2012-04-07 2:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 0:11 [PATCH] module: Clarify GPL-Compatible is OK Luis R. Rodriguez
2012-04-07 0:27 ` Greg Kroah-Hartman
2012-04-07 0:28 ` Al Viro
2012-04-07 0:57 ` Luis R. Rodriguez
2012-04-07 0:36 ` Linus Torvalds
2012-04-07 0:51 ` Luis R. Rodriguez
2012-04-07 1:02 ` Luis R. Rodriguez
2012-04-08 12:42 ` Arend van Spriel
2012-04-07 2:49 ` Ted Ts'o [this message]
2012-04-07 3:01 ` Luis R. Rodriguez
2012-04-07 21:15 ` Ted Ts'o
2012-04-08 0:52 ` Luis R. Rodriguez
2012-04-08 14:57 ` Alan Cox
2012-04-08 16:06 ` Luis R. Rodriguez
2012-04-08 17:12 ` Alan Cox
2012-04-08 20:23 ` Ted Ts'o
2012-04-07 19:03 ` Alan Cox
2012-04-08 12:49 ` Arend van Spriel
2012-04-08 22:50 ` Dan Williams
2012-05-07 2:39 ` Rusty Russell
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=20120407024941.GB11295@thunk.org \
--to=tytso@mit.edu \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.