linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Alan Cox <alan@linux.intel.com>, "Theodore Ts'o" <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ciaran Farrell <ciaran.farrell@suse.com>,
	Christopher De Nicolo <christopher.denicolo@suse.com>,
	Richard Fontana <fontana@sharpeleven.org>,
	Discussion and development of copyleft-next 
	<copyleft-next@lists.fedorahosted.org>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	Paul Bolle <pebolle@tiscali.nl>, Peter Anvin <hpa@zytor.com>,
	Joe Perches <joe@perches.com>
Subject: Re: [copyleft-next] Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)
Date: Fri, 19 May 2017 11:04:42 -0700	[thread overview]
Message-ID: <CAB=NE6VnftR-OR9iLFT3Lnbp4m35P0NFeGxNpRnAWvBbaemrFg@mail.gmail.com> (raw)
In-Reply-To: <20170519175912.GL8951@wotan.suse.de>

On Fri, May 19, 2017 at 10:59 AM, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
> On Fri, May 19, 2017 at 05:09:20PM +0200, Luis R. Rodriguez wrote:
>> On Fri, May 19, 2017 at 12:31:50PM +0100, Alan Cox wrote:
>> > > I really cannot see how you might have an attorney who wants ink on
>> > > 2A but not 1A.
>> > > I really cannot see how you might have an attorney who wants ink on
>> > > 2B but not 1B.
>> >
>> > Because their job is to protect their whomsoever they represent. They
>> > protect them drawing upon case law and providing rules based upon
>> > caselaw so that people don't have to keep bothering them.
>> >
>> > The lawyers have caselaw for "either a or b" licensing. They don't have
>> > caselaw for licence compatibility with your licence. Therefore it's a
>> > risk.
>>
>> Alright, this makes sense.
>>
>> As noted though there are a few "or" clauses, which upstream file
>> is a good template to use for copyleft-next ?
>
> There seems to be a few "or" clauses. For instance:
>
> a) you can pick either license [0]
> b) gpl on Linux, otherwise this other license below [1]
>
> To help uplift copyleft will go with b).
>
> [0] drivers/infiniband/hw/hfi1/driver.c
> [1] drivers/block/xen-blkback/blkback.c

So that yields:

 * This program is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License as published by the Free
 * Software Foundation; either version 2 of the License, or at your option) any
 * later version; or, when distributed separately from the Linux kernel or
 * incorporated into other software packages, subject to the following license:
 *
 * This program is free software; you can redistribute it and/or modify it
 * under the terms of copyleft-next (version 0.3.1 or later) as published
 * at http://copyleft-next.org/.

If there are issue please let me know.

  Luis

  reply	other threads:[~2017-05-19 18:06 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 18:35 [PATCH] module.h: add copyleft-next >= 0.3.1 as GPL compatible 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
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 [this message]
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='CAB=NE6VnftR-OR9iLFT3Lnbp4m35P0NFeGxNpRnAWvBbaemrFg@mail.gmail.com' \
    --to=mcgrof@kernel.org \
    --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=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rusty@rustcorp.com.au \
    --cc=takahiro.akashi@linaro.org \
    --cc=torvalds@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).