linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
	linux-can@vger.kernel.org,
	Stephane Grosjean <s.grosjean@peak-system.com>
Subject: Re: [PATCH v9 0/7] Add CAN FD infrastructure for CAN driver
Date: Tue, 04 Mar 2014 10:22:25 +0100	[thread overview]
Message-ID: <53159B51.4020704@pengutronix.de> (raw)
In-Reply-To: <1393601785-4631-1-git-send-email-socketcan@hartkopp.net>

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

On 02/28/2014 04:36 PM, Oliver Hartkopp wrote:
> This is the patch series to extend the CAN driver infrastructure with CAN FD.
> 
> Changes v8 -> v9:
> 
> Fixed a whitepace issue in patch 4 and added a comment about the different
> configuration options.
> 
> *** BLURB HERE ***
> 
> Oliver Hartkopp (7):
>   can: preserve skbuff protocol in can_put_echo_skb
>   can: only send bitrate data via netlink when available
>   can: move sanity check for bitrate and tq into can_get_bittiming
>   can: provide a separate bittiming_const parameter to bittiming
>     functions
>   can: introduce the data bitrate configuration for CAN FD
>   can: allow to change the device mtu for CAN FD capable devices
>   can: add bittiming check at interface open for CAN FD
> 
>  drivers/net/can/dev.c            | 160 ++++++++++++++++++++++++++++++---------
>  include/linux/can/dev.h          |   7 +-
>  include/uapi/linux/can/netlink.h |   3 +
>  3 files changed, 133 insertions(+), 37 deletions(-)

Stephane, I'll add your Acked-by that you have given for the v8 of this
series.

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]

  parent reply	other threads:[~2014-03-04  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 15:36 [PATCH v9 0/7] Add CAN FD infrastructure for CAN driver Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 1/7] can: preserve skbuff protocol in can_put_echo_skb Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 2/7] can: only send bitrate data via netlink when available Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 3/7] can: move sanity check for bitrate and tq into can_get_bittiming Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 4/7] can: provide a separate bittiming_const parameter to bittiming functions Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 5/7] can: introduce the data bitrate configuration for CAN FD Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 6/7] can: allow to change the device mtu for CAN FD capable devices Oliver Hartkopp
2014-02-28 15:36 ` [PATCH v9 7/7] can: add bittiming check at interface open for CAN FD Oliver Hartkopp
2014-03-04  9:22 ` Marc Kleine-Budde [this message]
2014-03-04 12:15   ` [PATCH v9 0/7] Add CAN FD infrastructure for CAN driver Stephane Grosjean

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=53159B51.4020704@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=s.grosjean@peak-system.com \
    --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).