From: Sasha Levin <sashal@kernel.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH 6.18.y] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering
Date: Tue, 25 Aug 2026 07:49:33 -0400 [thread overview]
Message-ID: <202608250013.6e9c30257cf35cff@kernel.org> (raw)
In-Reply-To: <376bdf5f-0e7f-4330-a3bd-7cffdc3ab857@hartkopp.net>
On Fri, Aug 21, 2026 at 09:00:21AM +0200, Oliver Hartkopp wrote:
> upstream commit 050f010f920da17c1044a4f174766ad553e770b6 is now
> integrated in 6.6.y , 6.12.y and 6.18.y
>
> But I didn't get a FAIL notice for 5.10.y 5.15.y 6.1.y so far.
No notice is coming for those, sorry - cf070fe33bfb reached 6.1.y, 5.15.y
and 5.10.y by a different route, so 050f010f920d was never auto-tried
against them and nothing generated a failure mail.
The gap is real though: all three carry cf070fe33bfb without its
follow-up. Could you send the same v2-style 2-patch series
(d4fb6514ff8e + 050f010f920d) for 6.1.y, 5.15.y and 5.10.y, threaded to
this mail?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-08-25 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:03 FAILED: patch "[PATCH] can: isotp: fix timer drain order, wakeup handling and tx_gen" failed to apply to 6.18-stable tree gregkh
2026-08-05 12:54 ` [PATCH 6.18.y] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering Oliver Hartkopp
2026-08-06 11:36 ` Sasha Levin
2026-08-06 12:09 ` Oliver Hartkopp
2026-08-06 17:40 ` Sasha Levin
2026-08-07 8:05 ` Oliver Hartkopp
2026-08-21 7:00 ` Oliver Hartkopp
2026-08-25 11:49 ` Sasha Levin [this message]
2026-08-25 12:27 ` [PATCH 5.10.y 1/2] can: use skb hash instead of private variable in headroom Oliver Hartkopp
2026-08-25 12:27 ` [PATCH 5.10.y 2/2] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering Oliver Hartkopp
2026-08-25 12:27 ` [PATCH 5.15.y 1/2] can: use skb hash instead of private variable in headroom Oliver Hartkopp
2026-08-25 12:27 ` [PATCH 5.15.y 2/2] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering Oliver Hartkopp
2026-08-25 12:27 ` [PATCH 6.1.y 1/2] can: use skb hash instead of private variable in headroom Oliver Hartkopp
2026-08-25 12:27 ` [PATCH 6.1.y 2/2] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering Oliver Hartkopp
2026-08-07 7:52 ` [PATCH 6.18.y v2 1/2] can: use skb hash instead of private variable in headroom Oliver Hartkopp
2026-08-07 7:52 ` [PATCH 6.18.y v2 2/2] can: isotp: fix timer drain order, wakeup handling and tx_gen ordering 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=202608250013.6e9c30257cf35cff@kernel.org \
--to=sashal@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stable@vger.kernel.org \
/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