linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-can@vger.kernel.org, kernel@pengutronix.de,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	Urs Thuermann <urs.thuermann@volkswagen.de>,
	Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH] linux/can: add explicit copyrights to can headers
Date: Fri, 06 Sep 2013 16:32:02 +0200	[thread overview]
Message-ID: <5229E762.6030605@pengutronix.de> (raw)
In-Reply-To: <1376858497-1700-1-git-send-email-u.kleine-koenig@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

On 08/18/2013 10:41 PM, Uwe Kleine-König wrote:
> These files are copied to the source code of user space applications (in
> this case can-utils) and so it makes sense to mention explicitly their
> copyright. I added the terms of C code that was introduced in the same
> commit as these headers.
> 
> Cc: Oliver Hartkopp <socketcan@hartkopp.net>
> Cc: Urs Thuermann <urs.thuermann@volkswagen.de>
> Cc: Wolfgang Grandegger <wg@grandegger.com>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> I think it is necessary to get the Ack of the three 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?
> 
> Best regards
> Uwe
> 
>  include/uapi/linux/can/bcm.h     | 32 ++++++++++++++++++++++++++++++++
>  include/uapi/linux/can/error.h   | 32 ++++++++++++++++++++++++++++++++
>  include/uapi/linux/can/gw.h      | 32 ++++++++++++++++++++++++++++++++
>  include/uapi/linux/can/netlink.h | 11 +++++++++++
>  include/uapi/linux/can/raw.h     | 32 ++++++++++++++++++++++++++++++++
>  5 files changed, 139 insertions(+)

If've ripped the can/netlink.h from this patch and resend it to the
mailinglist. I've pushed already Acked (by Oliver and Urs) parts to
linux-can-next/testing.

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 --]

  parent reply	other threads:[~2013-09-06 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 20:41 [PATCH] linux/can: add explicit copyrights to can headers Uwe Kleine-König
2013-08-19 17:13 ` Oliver Hartkopp
2013-09-06 14:32 ` Marc Kleine-Budde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-19  9:25 Thuermann, Urs, Dr. (K-EFFB/E)

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=5229E762.6030605@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=urs.thuermann@volkswagen.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).