From: "Arnd Bergmann" <arnd@arndb.de>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>,
Netdev <netdev@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
linux-can@vger.kernel.org,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Vincent Mailhol" <mailhol@kernel.org>
Subject: Re: [PATCH net 1/4] Revert "can: raw: instantly reject unsupported CAN frames"
Date: Thu, 15 Jan 2026 14:18:26 +0100 [thread overview]
Message-ID: <563a78e6-e1b0-4bc7-abc1-0c87da53972d@app.fastmail.com> (raw)
In-Reply-To: <20260115090603.1124860-2-mkl@pengutronix.de>
On Thu, Jan 15, 2026, at 09:57, Marc Kleine-Budde wrote:
> From: Oliver Hartkopp <socketcan@hartkopp.net>
>
> This reverts commit 1a620a723853a0f49703c317d52dc6b9602cbaa8
>
> and its follow-up fixes for the introduced dependency issues.
>
> commit 1a620a723853 ("can: raw: instantly reject unsupported CAN
> frames")
> commit cb2dc6d2869a ("can: Kconfig: select CAN driver infrastructure by
> default")
> commit 6abd4577bccc ("can: fix build dependency")
> commit 5a5aff6338c0 ("can: fix build dependency")
>
> The entire problem was caused by the requirement that a new network layer
> feature needed to know about the protocol capabilities of the CAN devices.
> Instead of accessing CAN device internal data structures which caused the
> dependency problems a better approach has been developed which makes use of
> CAN specific ml_priv data which is accessible from both sides.
>
> Cc: Marc Kleine-Budde <mkl@pengutronix.de>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Vincent Mailhol <mailhol@kernel.org>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Link: https://patch.msgid.link/20260109144135.8495-2-socketcan@hartkopp.net
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2026-01-15 13:18 UTC|newest]
Thread overview: 12+ 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 [this message]
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 ` [PATCH net 0/4] pull-request: can 2026-01-15 Jakub Kicinski
2026-01-16 7:34 ` Marc Kleine-Budde
2026-01-16 17:03 ` Marc Kleine-Budde
2026-01-17 17:30 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2026-01-14 10:44 [PATCH net 0/4] pull-request: can 2026-01-14 Marc Kleine-Budde
2026-01-14 10:45 ` [PATCH net 1/4] Revert "can: raw: instantly reject unsupported CAN frames" 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=563a78e6-e1b0-4bc7-abc1-0c87da53972d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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