LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Bodo Eggert <7eggert@gmx.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Andrew Morton <akpm@osdl.org>,
	Jon Masters <jonathan@jonmasters.org>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH/RFC] alternative aproach to: Ban module license tag string termination trick
Date: Mon, 5 Feb 2007 14:08:51 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.58.0702051342210.3110@be1.lrz> (raw)
In-Reply-To: <20070203200209.4f931fdc@localhost.localdomain>

On Sat, 3 Feb 2007, Alan wrote:
> Bodo Eggert <7eggert@gmx.de> wrote:

> > This patch changes the module license handling code to:
> > - allow modules to have multiple licenses
> 
> NAK

I still think it would be a good idea, but if too many people misinterpret 
my concept, you can't do that.

> > - access GPL symbols if at least one license is GPL-compatible
> 
> NAK
> 
> The legal boundary of a work is not "the file".

IMO, the scope of the MODULE_LICENSE is the module. If you intend to ship 
one binary using _only_ the proprietary license, you'll have to remove the 
license=GPL-string. Obviously this isn't obvious. :(

-- 
Backups? We doan NEED no steenking baX%^~,VbKx NO CARRIER 

      reply	other threads:[~2007-02-05 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-03  2:08 Bodo Eggert
2007-02-03  8:14 ` Russell King
2007-02-03 11:38   ` Jan Engelhardt
2007-02-03 19:56   ` Alan
2007-02-03 20:12     ` Randy Dunlap
2007-02-03 11:32 ` Jan Engelhardt
2007-02-03 11:54   ` Theodore Tso
2007-02-03 14:04   ` Bodo Eggert
2007-02-03 19:47     ` Alan
2007-02-03 20:02 ` Alan
2007-02-05 13:08   ` Bodo Eggert [this message]

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=Pine.LNX.4.58.0702051342210.3110@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH/RFC] alternative aproach to: Ban module license tag string termination trick' \
    /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

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).