From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] can: add explicit copyright to header can/netlink.h
Date: Tue, 10 Sep 2013 09:59:07 +0200 [thread overview]
Message-ID: <20130910075907.GB24802@pengutronix.de> (raw)
In-Reply-To: <522CD430.1020009@grandegger.com>
Hello Wolfgang,
On Sun, Sep 08, 2013 at 09:46:56PM +0200, Wolfgang Grandegger wrote:
> On 09/08/2013 09:09 PM, Oliver Hartkopp wrote:
> > 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.
INAL, too, but I think it's at least quite usual, even Linux' COPYING
does something like that:
NOTE! This copyright does *not* cover user programs that use kernel
services by normal system calls - this is merely considered normal use
of the kernel, and does *not* fall under the heading of "derived work".
One of the main issues of the GPL is the definition of "derived work".
There are discussions about kernel modules, extensions to userspace
programs, output generated by a program etc. pp. So I think it's fine to
explicitly note if you consider a certain usage of your code to be a
derived work or not. So I'd say such a statement is not a restriction
and so should be fine.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-09-10 7:59 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
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 [this message]
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=20130910075907.GB24802@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/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).