From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Wolfgang Grandegger" <wg@grandegger.com>,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] can: add explicit copyright to header can/netlink.h
Date: Sat, 07 Sep 2013 12:25:36 +0200 [thread overview]
Message-ID: <522AFF20.6000501@pengutronix.de> (raw)
In-Reply-To: <522AFEA8.3020303@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On 09/07/2013 12:23 PM, Oliver Hartkopp wrote:
> On 06.09.2013 21:37, Uwe Kleine-König wrote:
>
>>>> I think it is necessary to get the Ack of the people mentioned in
>>>> the Cc: commit footers. @Wolfgang: I added a statement
>>>>
>>>> The provided data structures and external interfaces from this code
>>>> are not restricted to be used by software with a GPL compatible
>>>> license.
>>>>
>>>> similar to the other can headers. Does that suit you?
>>>
>>> Is this the common phrase other public header files use as well?
>>> What's the motivation for that addition. Likely I might
>>> have missed some related discussion.
>> This is what the headers by Volkswagen are using, but it's only a
>> suggestion. So it's up to you.
>>
>
> Yep.
>
> To make clear that the CAN data structures should not be limited to be used in
> GPL code, this sentence has been added.
>
> E.g. to allow to implement a similar programming API for BSD, QNX or whatever
> which are obviously not GPL ...
>
> Don't know if this it suitable for the netlink stuff anyway.
The usage of netlink.h in a closed source app might be a nother usecase.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2013-09-07 10:26 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 [this message]
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
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=522AFF20.6000501@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=u.kleine-koenig@pengutronix.de \
--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).