[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221101074351.GA8310@amd>
Date: Tue, 1 Nov 2022 08:43:51 +0100
From: Pavel Machek <pavel@...x.de>
To: Biju Das <biju.das.jz@...renesas.com>
Cc: Wolfgang Grandegger <wg@...ndegger.com>,
gregkh@...uxfoundation.org, Marc Kleine-Budde <mkl@...gutronix.de>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Pavel Machek <pavel@...x.de>, Sasha Levin <sashal@...nel.org>,
linux-can@...r.kernel.org, netdev@...r.kernel.org,
Geert Uytterhoeven <geert+renesas@...der.be>,
Chris Paterson <chris.paterson2@...esas.com>,
linux-renesas-soc@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix
IRQ storm on global FIFO receive
Hi!
> Fixes: dd3bd23eb438 ("can: rcar_canfd: Add Renesas R-Car CAN FD driver")
> Suggested-by: Marc Kleine-Budde <mkl@...gutronix.de>
> Signed-off-by: Biju Das <biju.das.jz@...renesas.com>
> Link: https://lore.kernel.org/all/20221025155657.1426948-2-biju.das.jz@bp.renesas.com
> Cc: stable@...r.kernel.org#5.15.y
> [mkl: adjust commit message]
I got 7 or so copies of this, with slightly different Cc: lines.
AFAICT this is supposed to be stable kernel submission. In such case,
I'd expect [PATCH 4.14, 4.19, 5.10] in the subject line, and original
sign-off block from the mainline patch.
OTOH if it has Fixes tag (and it does) or Cc: stable (it has both),
normally there's no need to do separate submission to stable, as Greg
handles these automatically?
Thanks and best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists