All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH 3.6-rc1] canfd: remove redundant CAN FD flag
Date: Tue, 07 Aug 2012 10:33:16 +0200	[thread overview]
Message-ID: <5020D2CC.6040106@hartkopp.net> (raw)
In-Reply-To: <5020CEF7.9080809@pengutronix.de>

On 07.08.2012 10:16, Marc Kleine-Budde wrote:

> On 08/06/2012 06:02 PM, Oliver Hartkopp wrote:

>> The former flags definition turned out to be hard to use and is redundant in
>> the case of the CANFD_EDL flag.
>>
>> Do you want to take that patch in your linux-can tree to be pulled for 3.6-rc2
>> or should i send it to Dave/netdev-ML directly?
>> The patch is based on Linus' 3.6-rc1 tree.
> 
> I'll take the patch. As I'm the single point of contact, David will
> probably refuse to take it directly from you. I hope no one will blame
> us hard for modifying the ABI of the kernel for canfd frames. However I
> think it's okay as there are probably no users of the canfd frame out there.


Yes. We are the only users now and if you look at the patch in detail, i
removed these lines:

- * Btw. as long as there's no real implementation for CAN FD network driver
- * these bits are only preliminary.

Just if there's a discussion coming up.

From reading the CAN FD specs and the first controller register layout of the
M_CAN IP core the picture just settles :-)

> BTW: warning: 1 line adds whitespace errors.
> I've fixed this.


Many thanks!

Oliver


      reply	other threads:[~2012-08-07  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 16:02 [PATCH 3.6-rc1] canfd: remove redundant CAN FD flag Oliver Hartkopp
2012-08-07  8:16 ` Marc Kleine-Budde
2012-08-07  8:33   ` Oliver Hartkopp [this message]

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=5020D2CC.6040106@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.