All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: linux-kernel@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@frijolero.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>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK
Date: Mon, 07 May 2012 12:09:43 +0930	[thread overview]
Message-ID: <87ehqwhfyo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1333757482-16204-1-git-send-email-mcgrof@frijolero.org>

On Fri,  6 Apr 2012 17:11:22 -0700, "Luis R. Rodriguez" <mcgrof@frijolero.org> wrote:
> From: "Luis R. Rodriguez" <mcgrof@frijolero.org>
> 
> While the kernel is GPLv2 individual files and modules have
> historically been allowed to be:
> 
>   * Dual BSD/GPL
>   * Dual MIT/GPL
>   * Dual MPL/GPL
> 
> This is done for several reasons but most importantly to be able to
> share between Linux and permissive licensed Operating Systems such
> as the BSDs.

1) It's always better to be explicit.
2) Changing any licencing mark on a file is a PITA, involving acks and
   lawyers.
3) I haven't yet been overwhelmed with the burden of maintaining licence
   strings.

Thanks,
Rusty.

      parent reply	other threads:[~2012-05-07  5:24 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
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 [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=87ehqwhfyo.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --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=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.