From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Stephane Grosjean <s.grosjean@peak-system.com>,
Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH] can: add ability to allocate CANFD frame in skb data
Date: Thu, 16 Jan 2014 17:35:37 +0100 [thread overview]
Message-ID: <52D80A59.3020302@pengutronix.de> (raw)
In-Reply-To: <1389775813-14838-1-git-send-email-s.grosjean@peak-system.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On 01/15/2014 09:50 AM, Stephane Grosjean wrote:
> This patch adds the ability of allocating a CANFD frame data structure in the
> skb data area.
>
> Signed-off-by: Stephane Grosjean <s.grosjean@peak-system.com>
>
> ---
> drivers/net/can/dev.c | 24 ++++++++++++++++++++++++
> include/linux/can/dev.h | 2 ++
> 2 files changed, 26 insertions(+)
>
> diff --git a/drivers/net/can/dev.c b/drivers/net/can/dev.c
> index 13a9098..cb584ea 100644
> --- a/drivers/net/can/dev.c
> +++ b/drivers/net/can/dev.c
> @@ -521,6 +521,30 @@ struct sk_buff *alloc_can_skb(struct net_device *dev, struct can_frame **cf)
> }
> EXPORT_SYMBOL_GPL(alloc_can_skb);
>
> +struct sk_buff *alloc_canfd_skb(struct net_device *dev,
> + struct canfd_frame **cfd)
Originally "cf" stands for _c_an _f_rame, but cfd for for CAN-FD frames
ist nice, too :)
applied to can-next
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 --]
prev parent reply other threads:[~2014-01-16 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 8:50 [PATCH] can: add ability to allocate CANFD frame in skb data Stephane Grosjean
2014-01-15 12:58 ` Marc Kleine-Budde
2014-01-15 13:13 ` Stephane Grosjean
2014-01-15 17:35 ` Oliver Hartkopp
2014-01-16 16:35 ` Marc Kleine-Budde [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=52D80A59.3020302@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).