From: Vincent Mailhol <vincent.mailhol@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>,
linux-can@vger.kernel.org, "Stefan Mätje" <stefan.maetje@esd.eu>,
"Maxime Jayat" <maxime.jayat@mobile-devices.fr>
Subject: Re: can-next patches summary
Date: Mon, 29 Jan 2024 18:03:00 +0900 [thread overview]
Message-ID: <CAMZ6Rq+5QGrVuKadhU8_=GmK+TV52fJaqRZYw9XQfUhc9xmDKw@mail.gmail.com> (raw)
In-Reply-To: <21323546-0ea7-4506-a1aa-62f52452a8c6@hartkopp.net>
Hi Marc,
+cc: Maxime Jayat
+cc: Stefan Mätje
On Mon. 29 Jan 2024 at 05:42, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
> Hello Marc,
>
> can you please consider to upstream these three patches?
>
> [PATCH v5] canxl: add virtual CAN network identifier support
> https://lore.kernel.org/linux-can/20240128183758.68401-1-socketcan@hartkopp.net/
>
> [PATCH v3] can: bcm: add recvmsg flags for own, local and remote traffic
> https://lore.kernel.org/linux-can/20240120081018.2319-1-socketcan@hartkopp.net/
>
> [PATCH] can: isotp: support dynamic flow control parameters
> https://lore.kernel.org/linux-can/20231208165729.3011-1-socketcan@hartkopp.net/
To add to Oliver's wish list, could you have a look at this patch for
can (stable):
[PATCH] can: netlink: Fix TDCO calculation using the old data bittiming
https://lore.kernel.org/linux-can/40579c18-63c0-43a4-8d4c-f3a6c1c0b417@munic.io/
and this series for can-next:
[PATCH v11 0/2] can: esd: add support for esd GmbH PCIe/402 CAN interface
https://lore.kernel.org/linux-can/20231122160211.2110448-1-stefan.maetje@esd.eu/
to which I gave my review tag in:
https://lore.kernel.org/linux-can/CAMZ6RqJiCk_yc_V_1=TkJ41KjTQpDU--Z-kEwdUugoxMbz3G0A@mail.gmail.com/
Thank you,
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2024-01-29 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 20:36 can-next patches summary Oliver Hartkopp
2024-01-29 9:03 ` Vincent Mailhol [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='CAMZ6Rq+5QGrVuKadhU8_=GmK+TV52fJaqRZYw9XQfUhc9xmDKw@mail.gmail.com' \
--to=vincent.mailhol@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=maxime.jayat@mobile-devices.fr \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stefan.maetje@esd.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).