From: Jakub Kicinski <kuba@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH net 0/4] pull-request: can 2026-01-15
Date: Thu, 15 Jan 2026 18:51:10 -0800 [thread overview]
Message-ID: <20260115185110.6c4de645@kernel.org> (raw)
In-Reply-To: <20260115090603.1124860-1-mkl@pengutronix.de>
On Thu, 15 Jan 2026 09:57:07 +0100 Marc Kleine-Budde wrote:
> Hello netdev-team,
>
> this is a pull request of 4 patches for net/main, it super-seeds the
> "can 2026-01-14" pull request. The dev refcount leak in patch #3 is
> fixed.
>
> The first 3 patches are by Oliver Hartkopp and revert the approach to
> instantly reject unsupported CAN frames introduced in
> net-next-for-v6.19 and replace it by placing the needed data into the
> CAN specific ml_priv.
>
> The last patch is by Tetsuo Handa and fixes a J1939 refcount leak for
> j1939_session in session deactivation upon receiving the second RTS.
Hi Marc!
Was the AI wrong here
https://lore.kernel.org/all/20260110223836.3890248-1-kuba@kernel.org/
or that fix is still in the works?
next prev parent reply other threads:[~2026-01-16 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:57 [PATCH net 0/4] pull-request: can 2026-01-15 Marc Kleine-Budde
2026-01-15 8:57 ` [PATCH net 1/4] Revert "can: raw: instantly reject unsupported CAN frames" Marc Kleine-Budde
2026-01-15 12:20 ` patchwork-bot+netdevbpf
2026-01-15 13:18 ` Arnd Bergmann
2026-01-15 8:57 ` [PATCH net 2/4] can: propagate CAN device capabilities via ml_priv Marc Kleine-Budde
2026-01-15 8:57 ` [PATCH net 3/4] can: raw: instantly reject disabled CAN frames Marc Kleine-Budde
2026-01-15 8:57 ` [PATCH net 4/4] net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts Marc Kleine-Budde
2026-01-16 2:51 ` Jakub Kicinski [this message]
2026-01-16 7:34 ` [PATCH net 0/4] pull-request: can 2026-01-15 Marc Kleine-Budde
2026-01-16 17:03 ` Marc Kleine-Budde
2026-01-17 17:30 ` Jakub Kicinski
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=20260115185110.6c4de645@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@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 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.