From: Max Staudt <max@enpas.org>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Markus Schneider-Pargmann <msp@baylibre.com>,
Heiko Stuebner <heiko@sntech.de>,
Manivannan Sadhasivam <mani@kernel.org>,
Thomas Kopp <thomas.kopp@microchip.com>,
Ming Yu <tmyu0@nuvoton.com>
Cc: kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
NXP S32 Linux Team <s32@nxp.com>,
imx@lists.linux.dev, Haibo Chen <haibo.chen@nxp.com>,
Enric Balletbo <eballetb@redhat.com>
Subject: Re: [PATCH v6 1/3] can: at91_can: release the rx-offload on teardown
Date: Sat, 26 Sep 2026 23:53:56 +0900 [thread overview]
Message-ID: <93a9dbca-4f3b-4b01-8e07-1dbc7035a96d@enpas.org> (raw)
In-Reply-To: <20260925144558.2909639-2-ciprianmarian.costea@oss.nxp.com>
This is not my driver, but the patch looks reasonable to me. While we
wait for someone else's proper review, let's call it
Acked-by: Max Staudt <max@enpas.org>
Thank you!
next prev parent reply other threads:[~2026-09-26 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:45 [PATCH v6 0/3] can: rx-offload: add a per-IRQ receive context Ciprian Costea
2026-09-25 14:45 ` [PATCH v6 1/3] can: at91_can: release the rx-offload on teardown Ciprian Costea
2026-09-26 14:53 ` Max Staudt [this message]
2026-09-25 14:45 ` [PATCH v6 2/3] can: rx-offload: add a per-IRQ receive context Ciprian Costea
2026-09-26 15:26 ` Max Staudt
2026-09-25 14:45 ` [PATCH v6 3/3] can: flexcan: use one rx-offload context per IRQ line Ciprian Costea
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=93a9dbca-4f3b-4b01-8e07-1dbc7035a96d@enpas.org \
--to=max@enpas.org \
--cc=alexandre.belloni@bootlin.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dario.binacchi@amarulasolutions.com \
--cc=eballetb@redhat.com \
--cc=haibo.chen@nxp.com \
--cc=heiko@sntech.de \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mailhol@kernel.org \
--cc=mani@kernel.org \
--cc=mkl@pengutronix.de \
--cc=msp@baylibre.com \
--cc=nicolas.ferre@microchip.com \
--cc=s32@nxp.com \
--cc=thomas.kopp@microchip.com \
--cc=tmyu0@nuvoton.com \
/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
all inboxes | Powered by JetHome®