All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] can: add explicit copyright to header can/netlink.h
Date: Sun, 08 Sep 2013 21:46:56 +0200	[thread overview]
Message-ID: <522CD430.1020009@grandegger.com> (raw)
In-Reply-To: <522CCB73.3090504@hartkopp.net>

On 09/08/2013 09:09 PM, Oliver Hartkopp wrote:
> On 07.09.2013 21:15, Wolfgang Grandegger wrote:
>> On Sat, 07 Sep 2013 12:25:36 +0200, Marc Kleine-Budde <mkl@pengutronix.de>
> 
> 
>>> The usage of netlink.h in a closed source app might be a nother usecase.
>>
>>
>>
>> The intention is clear. But many other uapi include files are used in
>>
>> closed source as well without such a clause.
>>
>>
>>
>> Are you/we sure that this addition is even compatible with the
>>
>> GPL (v2) license. GPL does usually not allow exceptions.
> 
> As original author you may chose the license as you like.
> 
> That's why our license header intends to be like a BSD license and when used
> inside the Linux kernel the GPL comes into action:
> 
>  * Alternatively, provided that this notice is retained in full, this
>  * software may be distributed under the terms of the GNU General
>  * Public License ("GPL") version 2, in which case the provisions of the
>  * GPL apply INSTEAD OF those given above.
> 
> And then - just to make it really sure - this additional sentence is written:
> 
>  * The provided data structures and external interfaces from this code
>  * are not restricted to be used by modules with a GPL compatible license.

The question is if this sentence is a legal addition to the GPL license.
I personally doubt but I'm not a lawyer.

Wolfgang.


  reply	other threads:[~2013-09-08 19:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 14:30 [PATCH] can: add explicit copyright to header can/netlink.h Marc Kleine-Budde
2013-09-06 15:48 ` Wolfgang Grandegger
2013-09-06 19:37   ` Uwe Kleine-König
2013-09-06 20:35     ` Wolfgang Grandegger
2013-09-06 20:45       ` Uwe Kleine-König
2013-09-06 21:05         ` Wolfgang Grandegger
2013-09-07 19:34           ` [PATCH] uapi/linux/can: add explicit copyrights to can's netlink header Uwe Kleine-König
2013-09-07 19:57             ` Wolfgang Grandegger
2013-09-07 20:03               ` Marc Kleine-Budde
2013-09-07 10:23     ` [PATCH] can: add explicit copyright to header can/netlink.h Oliver Hartkopp
2013-09-07 10:25       ` Marc Kleine-Budde
2013-09-07 19:15         ` Wolfgang Grandegger
2013-09-08 19:09           ` Oliver Hartkopp
2013-09-08 19:46             ` Wolfgang Grandegger [this message]
2013-09-09 18:06               ` Oliver Hartkopp
2013-09-09 20:01                 ` Wolfgang Grandegger
2013-09-09 20:29                   ` Oliver Hartkopp
2013-09-10  7:59               ` Uwe Kleine-König
2013-09-10 10:19                 ` Wolfgang Grandegger

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=522CD430.1020009@grandegger.com \
    --to=wg@grandegger.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.