mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: gregkh@linuxfoundation.org, rusty@rustcorp.com.au,
	linux-kernel@vger.kernel.org, ciaran.farrell@suse.com,
	christopher.denicolo@suse.com, fontana@sharpeleven.org,
	copyleft-next@lists.fedorahosted.org, gnomes@lxorguk.ukuu.org.uk,
	alan@linux.intel.com, tytso@mit.edu, hpa@zytor.com
Subject: Re: [PATCH] module.h: add copyleft-next >= 0.3.1 as GPL compatible
Date: Wed, 29 Jun 2016 23:43:33 +0200	[thread overview]
Message-ID: <1467236613.26658.47.camel@tiscali.nl> (raw)
In-Reply-To: <20160629190547.GB31219@wotan.suse.de>

On wo, 2016-06-29 at 21:05 +0200, Luis R. Rodriguez wrote:
> I haven't seen any objections or questions, so just a friendly *poke*.

At the end of the day, what matters most is whether a module is GPL v2
compatible. So why are the specific license idents for the various GPL
v2 compatible licenses actually needed?

include/linux/module.h tells us:
    1.   So modinfo can show license info for users wanting to vet their setup
         is free
    2.   So the community can ignore bug reports including proprietary modules
    3.   So vendors can do likewise based on their own policies

Does that require more than just two license idents ("GPL v2 compatible"
and "Proprietary")?


Paul Bolle

  parent reply	other threads:[~2016-06-29 21:44 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 18:35 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 [this message]
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               ` [copyleft-next] " Luis R. Rodriguez
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=1467236613.26658.47.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=alan@linux.intel.com \
    --cc=christopher.denicolo@suse.com \
    --cc=ciaran.farrell@suse.com \
    --cc=copyleft-next@lists.fedorahosted.org \
    --cc=fontana@sharpeleven.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tytso@mit.edu \
    /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
all inboxes | Powered by JetHome®