From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v2 0/3] CAN netlayer fixes for stable
Date: Mon, 28 Sep 2026 21:37:18 +0200 [thread overview]
Message-ID: <07764aa7-e46f-42a2-b2a9-b4fdb3411b48@hartkopp.net> (raw)
In-Reply-To: <c3fa6f4e-d19b-42eb-93ac-bd694a666aa3@hartkopp.net>
Btw. the first two patches of this patch set might go in immediately.
On 28.09.26 21:26, Oliver Hartkopp wrote:
>
>
> On 28.09.26 20:43, Marc Kleine-Budde wrote:
>> On 28.09.2026 19:31:02, Oliver Hartkopp wrote:
>>> This patch set aggregates the open stable fixes for the CAN netlayer.
>>>
>>> v2: restore non-zero UID value generation for isotp cfecho handling
>>
>> I'll send a PR soonish. Once this series is ready, I'll send another PR.
>
> Thanks Marc!
>
> I've updated a v3 - maybe sashiko is fine now :-D
>
> Best regards,
> Oliver
>
>
next prev parent reply other threads:[~2026-09-28 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 17:31 [PATCH v2 0/3] CAN netlayer fixes for stable Oliver Hartkopp
2026-09-28 17:31 ` [PATCH v2 1/3] can: remove CAN filters independent from namespace Oliver Hartkopp
2026-09-28 17:31 ` [PATCH v2 2/3] can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv() Oliver Hartkopp
2026-09-28 17:31 ` [PATCH v2 3/3] can: fix unique skb identifier regression under RPS Oliver Hartkopp
2026-09-28 17:48 ` sashiko-bot
2026-09-28 18:43 ` [PATCH v2 0/3] CAN netlayer fixes for stable Marc Kleine-Budde
2026-09-28 19:26 ` Oliver Hartkopp
2026-09-28 19:37 ` Oliver Hartkopp [this message]
2026-09-29 17:07 ` v5 is ready - " Oliver Hartkopp
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=07764aa7-e46f-42a2-b2a9-b4fdb3411b48@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--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