linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Subject: Re: [PATCH v5 5/5] include: Move includes copied from the Linux kernel into include/linux
Date: Tue, 21 Jan 2014 10:53:37 +0100	[thread overview]
Message-ID: <20140121095337.GR25911@pengutronix.de> (raw)
In-Reply-To: <52DA7106.5000300@hartkopp.net>

On Sat, Jan 18, 2014 at 01:18:14PM +0100, Oliver Hartkopp wrote:
> On 17.01.2014 21:36, Uwe Kleine-König wrote:
> 
> >>
> >> https://gitorious.org/linux-can/can-modules
> > Is it a possibility to merge can-modules and can-utils?
> 
> NO!
Did I hit another red button? If so I'm sorry, that was not my
intention.

> > Then there would
> > only a single instance of isotp.h be needed. 
> 
> NO!
?? If can-modules and can-utils were merged both the kernel module and
the userspace stuff could use the same header. I don't understand you
"NO!" here.

> [...]
I don't see a real reason here, but I read between the lines that you
prefer isotp to go into the kernel directly instead of into can-utils
first.
Anyhow, what I care for is to be able to package can-utils for Debian.
That's what I can do once the updated headers hit can-utils so IMO we
can stop arguing even if we don't agree 100%.

@Marc or Oliver: Can you please give me a ping as soon as the headers
hit your public repo. Thanks.

Best regards
Uwe

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

  reply	other threads:[~2014-01-21  9:53 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
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 [this message]
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=20140121095337.GR25911@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    /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).