From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "Stefan Mätje" <Stefan.Maetje@esd.eu>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: "mailhol.vincent@wanadoo.fr" <mailhol.vincent@wanadoo.fr>,
"mkl@pengutronix.de" <mkl@pengutronix.de>
Subject: Re: [PATCH v8] can-dev: add len8_dlc support for various CAN adapters
Date: Wed, 11 Nov 2020 19:16:53 +0100 [thread overview]
Message-ID: <531de8eb-42c0-77dd-388a-07c7e74ce80b@hartkopp.net> (raw)
In-Reply-To: <4ef80738553cb4787d5a3146e2f696829b3dd9e6.camel@esd.eu>
Hi Stefan,
On 11.11.20 13:58, Stefan Mätje wrote:
> I would like to jump on the rolling train for the Classical CAN driver
> in
>
> - esd_usb2
>
> that supports the esd CAN-USB/2 and CAN-USB/Micro devices and add the
> CAN_CTRLMODE_CC_LEN8_DLC capability. At least I could do some tests
> with both devices.
Great! Thanks for your support!
> Am I right with the assumption that your patches are based on the
> linux-can tree?
No. The patches were originally based on the net-next tree:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
But you can now use the 'testing' branch of linux-can-next as Marc
applied the patches there for the upstream process:
https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=testing
> At the moment I'm in home-office and therefore will only on Friday
> again have access to my Linux test machine and the USB devices.
You would also need the updated can-utils which are currently only on my
personal fork:
https://github.com/hartkopp/can-utils
I need to start a pull request :-)
And you would need to extend the 'ip' tool from
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git
with this patch:
https://lore.kernel.org/linux-can/20201029083326.41627-1-socketcan@hartkopp.net/
Best regards,
Oliver
next prev parent reply other threads:[~2020-11-11 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 9:59 [PATCH v8] can-dev: add len8_dlc support for various CAN adapters Oliver Hartkopp
2020-11-11 10:13 ` Oliver Hartkopp
2020-11-11 12:58 ` Stefan Mätje
2020-11-11 18:16 ` Oliver Hartkopp [this message]
2020-11-11 13:54 ` 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=531de8eb-42c0-77dd-388a-07c7e74ce80b@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=Stefan.Maetje@esd.eu \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--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 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).