From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: 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: Fri, 6 Sep 2013 21:37:44 +0200 [thread overview]
Message-ID: <20130906193744.GV24802@pengutronix.de> (raw)
In-Reply-To: <ecac65a6d53af596b53d115a9e6552a0@grandegger.com>
Hello Wolfgang,
On Fri, Sep 06, 2013 at 05:48:06PM +0200, Wolfgang Grandegger wrote:
> Hi Marc and Uwe,
>
> On Fri, 6 Sep 2013 16:30:11 +0200, Marc Kleine-Budde <mkl@pengutronix.de>
> wrote:
> > From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >
> > This file is copied to the source code of user space applications (in
> > this case can-utils) and so it makes sense to mention explicitly its
> > copyright. I added the terms of C code that was introduced in the same
> > commit as this header.
> >
> > Cc: Wolfgang Grandegger <wg@grandegger.com>
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> > ---
> > Hello Wolfgang,
> >
> > this is the remaining hunk from Uwe's patch that has not been Acked.
> > Continuing
> > with Uwe's words (adopted):
> >
> > 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.
Best regards
Uwe
>
>
>
> Thanks,
>
>
>
> Wolfgang.
>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-09-06 19:37 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 [this message]
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
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=20130906193744.GV24802@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@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).