From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Biju Das <biju.das.jz@bp.renesas.com>, Pavel Machek <pavel@denx.de>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Sasha Levin <sashal@kernel.org>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO receive
Date: Tue, 1 Nov 2022 19:36:20 +0700 [thread overview]
Message-ID: <83d70f8f-419c-2eb9-5130-782750772868@gmail.com> (raw)
In-Reply-To: <OS0PR01MB59222BA2B1CAA6CDA9B4137486369@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 11/1/22 14:59, Biju Das wrote:
>> I got 7 or so copies of this, with slightly different Cc: lines.
>
> I followed option 1 mentioned in [1]
> > [1] https://www.kernel.org/doc/html/v5.10/process/stable-kernel-rules.html
>
>
>>
>> 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.
>
> OK. Maybe [1] needs updating.
The documentation says (in this case the third option applies):
> Send the patch, after verifying that it follows the above rules, to> stable@vger.kernel.org. You must note the upstream commit ID in the
> changelog of your submission, as well as the kernel version you wish
> it to be applied to.
It doesn't specify how to mark desired target branch, unfortunately.
>
>>
>> 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?
>
> I got merge conflict mails for 4.9, 4.14, 4.19, 5.4, 5.10 and 5.15 stable.
> I thought, I need to fix the conflicts and resend. Am I missing anything?? Please let me know.
>
The upstream commit didn't apply cleanly to *all* stable branches due
to conflicts, right?
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-11-01 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 14:33 [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO receive Biju Das
2022-11-01 7:43 ` Pavel Machek
2022-11-01 7:59 ` Biju Das
2022-11-01 12:36 ` Bagas Sanjaya [this message]
2022-11-01 13:32 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 13:26 Biju Das
2022-10-31 12:50 Biju Das
2022-10-31 11:50 Biju Das
2022-10-31 9:35 Biju Das
2022-10-31 9:04 Biju Das
2022-11-02 1:36 ` Greg KH
2022-10-31 9:02 Biju Das
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=83d70f8f-419c-2eb9-5130-782750772868@gmail.com \
--to=bagasdotme@gmail.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pavel@denx.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).