All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>, linux-can@vger.kernel.org
Cc: kernel@pengutronix.de
Subject: Re: [PATCH v12 0/7] Add CAN FD infrastructure for CAN driver
Date: Wed, 05 Mar 2014 08:16:39 +0100	[thread overview]
Message-ID: <5316CF57.7050609@hartkopp.net> (raw)
In-Reply-To: <1393972016-18383-1-git-send-email-mkl@pengutronix.de>



On 04.03.2014 23:26, Marc Kleine-Budde wrote:
> Again, it's me messing with Oliver's patches. (I think it's with).
> 
> changes since v11:
> - 3/7 + 4/7 Moved section about return value simplification from 3/7 -> 4/7
> 

I finally compared the result of this patch set to my v9. Looks good.

IMO the patches can be applied.

Thanks,
Oliver

      parent reply	other threads:[~2014-03-05  7:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 22:26 [PATCH v12 0/7] Add CAN FD infrastructure for CAN driver Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 1/7] can: preserve skbuff protocol in can_put_echo_skb Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 2/7] can: only send bitrate data via netlink when available Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 3/7] can: move sanity check for bitrate and tq into can_get_bittiming Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 4/7] can: provide a separate bittiming_const parameter to bittiming functions Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 5/7] can: introduce the data bitrate configuration for CAN FD Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 6/7] can: allow to change the device mtu for CAN FD capable devices Marc Kleine-Budde
2014-03-04 22:26 ` [PATCH v12 7/7] can: add bittiming check at interface open for CAN FD Marc Kleine-Budde
2014-03-05  7:16 ` 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=5316CF57.7050609@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=kernel@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 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.