linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v5 5/5] include: Move includes copied from the Linux kernel into include/linux
Date: Fri, 17 Jan 2014 14:37:09 +0100	[thread overview]
Message-ID: <20140117133709.GD25911@pengutronix.de> (raw)
In-Reply-To: <52D85910.8000200@pengutronix.de>

Hallo Marc,

On Thu, Jan 16, 2014 at 11:11:28PM +0100, Marc Kleine-Budde wrote:
> On 01/16/2014 08:28 PM, Uwe Kleine-König wrote:
> > On Thu, Jan 16, 2014 at 05:12:34PM +0100, Marc Kleine-Budde wrote:
> >> From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> >>
> >> This makes it possible to update the copies more easily, e.g.:
> >>
> >> 	cd $path_to_linux_repo
> >> 	make headers_install
> >> 	rsync -a --delete --exclude .\* usr/include/linux/can* $path_to_can_utils/include/linux
> >>
> >> Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
> >> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> 
> > I want to have pointed out in the commit log that it was you who added
> > isotp.h to the move. I don't care that much for your split into two
> > patches to fix the #includes first, but IMHO that should be documented,
> > too.
> 
> Yes, but no. I imported the isotp header, but not from the kernel. It
> was imported from the berlios svn repo.
I didn't mean isotp when it was added to can-utils, but compared to my
patch "include: Move includes copied from the Linux kernel into
include/linux" you also moved isotp.h from socketcan/can to linux/can in
can-utils. That's what I thought you should point out. That this change
makes the changelog wrong is another issue.

Where can this external kernel module be found? IMHO it would be worth
to point to its (hopefully) git repository in isotp{*.c,.h}.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2014-01-17 13:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 16:12 [PATCH v5 1/5] License cleanup Marc Kleine-Budde
2014-01-16 16:12 ` [PATCH v5 1/5] include: Remove two unused header files Marc Kleine-Budde
2014-01-16 16:12 ` [PATCH v5 2/5] ioctl.h: drop unused header Marc Kleine-Budde
2014-01-16 16:12 ` [PATCH v5 3/5] isotp.h: add explicit license information Marc Kleine-Budde
2014-01-16 16:12 ` [PATCH v5 4/5] include/socketcan: prepare headers to be moved to include/linux Marc Kleine-Budde
2014-01-16 16:12 ` [PATCH v5 5/5] include: Move includes copied from the Linux kernel into include/linux Marc Kleine-Budde
2014-01-16 19:28   ` Uwe Kleine-König
2014-01-16 22:11     ` Marc Kleine-Budde
2014-01-17 13:37       ` Uwe Kleine-König [this message]
2014-01-17 14:04         ` Marc Kleine-Budde
2014-01-17 20:36           ` Uwe Kleine-König
2014-01-18 12:18             ` Oliver Hartkopp
2014-01-21  9:53               ` Uwe Kleine-König
2014-01-21  9:59                 ` Yegor Yefremov
2014-01-21 10:32                   ` Uwe Kleine-König
2014-01-21 11:34                 ` Oliver Hartkopp
2014-01-21 11:37                   ` Marc Kleine-Budde
2014-01-21 11:51                     ` Oliver Hartkopp
2014-01-21 12:56                   ` Uwe Kleine-König

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=20140117133709.GD25911@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@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 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).