From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org, stable@kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH] can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv()
Date: Wed, 26 Aug 2026 13:43:53 +0200 [thread overview]
Message-ID: <20260826-loutish-cinnamon-macaw-e340a9-mkl@pengutronix.de> (raw)
In-Reply-To: <c3fc21b4-db28-4323-b182-eeeb646e64da@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On 25.08.2026 16:55:39, Oliver Hartkopp wrote:
> as you are currently filling your linux-can git repo, please take care of
> this (stable) patch too.
done
> Do you think that these two patches below should be integrated into a net
> pull?
"net" or "net-next"?
> [can-next v2] can: proc: remove pointers from CAN specific proc output
> https://lore.kernel.org/linux-can/20260815103400.117175-1-socketcan@hartkopp.net/
I've replied to that mail with some formatting nitpicks.
> [can-next] can: remove Softing CANcard driver
> https://lore.kernel.org/linux-can/20260815103428.117201-1-socketcan@hartkopp.net/
-> net-next material.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-26 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:08 [PATCH] can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv() Oliver Hartkopp
2026-08-19 16:26 ` sashiko-bot
2026-08-19 17:05 ` Oliver Hartkopp
2026-08-25 14:55 ` Oliver Hartkopp
2026-08-26 11:43 ` Marc Kleine-Budde [this message]
2026-08-26 19:34 ` Oliver Hartkopp
2026-08-27 6:22 ` Sebastian Andrzej Siewior
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=20260826-loutish-cinnamon-macaw-e340a9-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stable@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