From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-can@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>,
Yegor Yefremov <yegorslists@googlemail.com>
Subject: Re: [PATCH can-utils v2 1/3] headers: use include/linux only for Linux kernel headers
Date: Mon, 13 Jan 2014 22:31:56 +0100 [thread overview]
Message-ID: <52D45B4C.3070009@hartkopp.net> (raw)
In-Reply-To: <20140113212658.GL29475@pengutronix.de>
On 13.01.2014 22:26, Uwe Kleine-König wrote:
> Hello Oliver,
>
> On Mon, Jan 13, 2014 at 10:18:04PM +0100, Oliver Hartkopp wrote:
>> On 13.01.2014 21:45, Uwe Kleine-König wrote:
>>> On Mon, Jan 13, 2014 at 07:25:20PM +0100, Oliver Hartkopp wrote:
>>>> On 13.01.2014 08:20, Uwe Kleine-König wrote:
>>>>> On Mon, Jan 13, 2014 at 07:23:55AM +0100, Oliver Hartkopp wrote:
>>>>>> And e.g. this
>>>>>>
>>>>>>> #include <linux/can.h>
>>>>>>> -#include <linux/can/isotp.h>
>>>>>>> +#include "isotp.h"
>>>>>>> #include <linux/if_tun.h>
>>>>>>
>>>>>> should be avoided too.
>>>>> Why?
>>>>
>>>> When isotp hits the kernel, there's no need to adapt all userland programs.
> To be honest, it's not that hard to update all userland programs. I did
> it with:
>
> perl -p -i -e 's,^#include <whatever/can/isotp.h>$,#include "isotp.h",' isotp*
>
> (well, plus some reformatting, but meh).
>
>>> ah, didn't know that isotp targets the kernel. There is nothing in next
>>> yet. I wonder if it's sensible to put it into can-utils' copy of the
>>> kernel headers then. If you ask me keep isotp.h in / until it hits the
>>> kernel, then sync the headers and switch the programs explicitly. Only
>>> my 0.02 €.
>>
>> What's the benefit of moving it to root and then moving it back to the includes?
> The benefit is that there is less chance for surprises. Updating the
> kernel header copy still has a manual component when there are files in
> can-utils that are not existing in the kernel. Also I like changes to be
> explicit. When isotp.h is now kept in can-utils/include/linux and later
> hits the kernel there is no explicit commit that marks the start of
> using the kernel header and changing the procedure how to sync kernel
> headers. YMMV
>
>> Please let it stay in the current place.
> To late for v3, only read your mail when I sent it out.
>
Sorry that I did not was faster.
But it's never too late for my NACK for the "[PATCH can-utils v3 2/5] Move
isotp.h into the project root" :-)
To all the other stuff you may add my Acked-by: in the next attempt.
Btw. did you test the stuff on the 'old' system as you mentioned?
Regards,
Oliver
next prev parent reply other threads:[~2014-01-13 21:32 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 19:05 license issues of can-utils Uwe Kleine-König
2013-08-17 20:24 ` Marc Kleine-Budde
2013-08-18 10:26 ` Oliver Hartkopp
2014-01-11 23:10 ` [PATCH can-utils 0/3] License cleanup Uwe Kleine-König
2014-01-11 23:10 ` [PATCH can-utils 1/3] Update license information for some header files Uwe Kleine-König
2014-01-12 10:09 ` Oliver Hartkopp
2014-01-12 19:02 ` [PATCH] can: add explicit copyrights to can userspace header Uwe Kleine-König
2014-01-12 19:27 ` Oliver Hartkopp
2014-01-16 16:27 ` Marc Kleine-Budde
2014-01-12 19:53 ` [PATCH can-utils 1/3] Update license information for some header files Uwe Kleine-König
2014-01-11 23:10 ` [PATCH can-utils 2/3] ioctl.h: drop unused header Uwe Kleine-König
2014-01-12 10:18 ` Oliver Hartkopp
2014-01-11 23:10 ` [PATCH can-utils 3/3] slcand: remove program as it is undistributable Uwe Kleine-König
2014-01-11 23:38 ` Yegor Yefremov
2014-01-12 10:57 ` Oliver Hartkopp
2014-01-12 16:09 ` Yegor Yefremov
2014-01-12 18:22 ` Oliver Hartkopp
2014-01-12 19:54 ` Yegor Yefremov
2014-01-12 19:59 ` Oliver Hartkopp
2014-01-12 21:24 ` [PATCH can-utils v2 0/3] License cleanup Uwe Kleine-König
2014-01-12 21:24 ` [PATCH can-utils v2 1/3] headers: use include/linux only for Linux kernel headers Uwe Kleine-König
2014-01-13 6:23 ` Oliver Hartkopp
2014-01-13 7:20 ` Uwe Kleine-König
2014-01-13 18:25 ` Oliver Hartkopp
2014-01-13 20:45 ` Uwe Kleine-König
2014-01-13 21:18 ` Oliver Hartkopp
2014-01-13 21:26 ` Uwe Kleine-König
2014-01-13 21:31 ` Oliver Hartkopp [this message]
2014-01-13 21:37 ` Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 0/4] License cleanup Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 1/4] Remove two unused header files Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 2/4] Move includes copied from the Linux kernel into include/linux Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 3/4] ioctl.h: drop unused header Uwe Kleine-König
2014-01-13 21:57 ` [PATCH can-utils v4 4/4] isotp.h: add explicit license information Uwe Kleine-König
2014-01-14 7:01 ` Oliver Hartkopp
2014-01-14 8:46 ` Uwe Kleine-König
2014-01-14 15:49 ` Oliver Hartkopp
2014-01-16 19:18 ` Uwe Kleine-König
2014-01-16 22:05 ` Marc Kleine-Budde
2014-01-12 21:24 ` [PATCH can-utils v2 2/3] ioctl.h: drop unused header Uwe Kleine-König
2014-01-12 21:24 ` [PATCH can-utils v2 3/3] isotp.h: add explicit license information 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=52D45B4C.3070009@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yegorslists@googlemail.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).