From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
Cc: linux-can <linux-can@vger.kernel.org>,
Oliver Hartkopp <socketcan@hartkopp.net>
Subject: Re: [net-next v3 00/15] can: dev: cleanup and add CAN frame length handling support
Date: Tue, 12 Jan 2021 14:28:59 +0100 [thread overview]
Message-ID: <40a6ac73-4228-1557-6b45-a854e36fd083@pengutronix.de> (raw)
In-Reply-To: <CAMZ6RqJ=dr9SnP6YAF7WSKff7tYkqnoTZS7zjgSV1u3=TsQYTw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 489 bytes --]
On 1/12/21 2:14 PM, Vincent MAILHOL wrote:
> Reviewed-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>
> Reviewed and tested the patch series, everything is OK for me.
Updates the patches.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-01-12 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:19 [net-next v3 00/15] can: dev: cleanup and add CAN frame length handling support Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 01/15] MAINTAINERS: CAN network layer: add missing header file can-ml.h Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 02/15] can: dev: move driver related infrastructure into separate subdir Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 03/15] can: dev: move bittiming related code into seperate file Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 04/15] can: dev: move length " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 05/15] can: dev: move skb related " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 06/15] can: dev: move netlink related code " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 07/15] can: length: convert to kernel coding style Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 08/15] can: length: can_fd_len2dlc(): simplify length calculcation Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 09/15] can: length: canfd_sanitize_len(): add function to sanitize CAN-FD data length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 10/15] can: length: can_skb_get_frame_len(): introduce function to get data length of frame in data link layer Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 11/15] can: dev: extend struct can_skb_priv to hold CAN frame length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 12/15] can: dev: can_put_echo_skb(): extend to handle frame_len Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 13/15] can: dev: can_get_echo_skb(): extend to return can frame length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 14/15] can: dev: can_rx_offload_get_echo_skb(): " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 15/15] can: dev: add software tx timestamps Marc Kleine-Budde
2021-01-12 13:14 ` [net-next v3 00/15] can: dev: cleanup and add CAN frame length handling support Vincent MAILHOL
2021-01-12 13:28 ` 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=40a6ac73-4228-1557-6b45-a854e36fd083@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--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).