From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, mailhol.vincent@wanadoo.fr
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Introduce optional DLC element for Classic CAN
Date: Tue, 3 Nov 2020 23:27:09 +0100 [thread overview]
Message-ID: <e561625a-f6bb-bd10-332b-53cc2ae104b0@pengutronix.de> (raw)
In-Reply-To: <08cf2c95-df53-9ecb-d84a-9d95239b4b04@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 624 bytes --]
On 11/3/20 11:26 PM, Marc Kleine-Budde wrote:
> On 11/3/20 11:33 AM, Oliver Hartkopp wrote:
>> Hello Marc,
>>
>> I did some more testing with different CAN-USB adapters and feel pretty
>> comfortable on the below patch set now.
>>
>> Would you think this is something for can-next?
>
> Yes, this would go via
...net-next/master
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 --]
next prev parent reply other threads:[~2020-11-03 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 8:32 [PATCH v3 0/4] Introduce optional DLC element for Classic CAN Oliver Hartkopp
2020-10-29 8:32 ` [PATCH v3 1/4] can: add optional DLC element to Classical CAN frame structure Oliver Hartkopp
2020-11-03 15:03 ` Vincent MAILHOL
2020-10-29 8:32 ` [PATCH v3 2/4] can: rename get_can_dlc() macro with can_get_cc_len() Oliver Hartkopp
2020-11-03 15:17 ` Vincent MAILHOL
2020-11-03 18:45 ` Oliver Hartkopp
2020-10-29 8:32 ` [PATCH v3 3/4] can: remove obsolete get_canfd_dlc() macro Oliver Hartkopp
2020-10-29 8:32 ` [PATCH v3 4/4] can: replace can_dlc as variable/element for payload length Oliver Hartkopp
2020-11-03 10:33 ` [PATCH v3 0/4] Introduce optional DLC element for Classic CAN Oliver Hartkopp
2020-11-03 22:26 ` Marc Kleine-Budde
2020-11-03 22:27 ` Marc Kleine-Budde [this message]
2020-11-04 15:08 ` Oliver Hartkopp
2020-11-04 15:15 ` Marc Kleine-Budde
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=e561625a-f6bb-bd10-332b-53cc2ae104b0@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 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.