Re: [PATCH] can: rcar_canfd: rcar_canfd_handle_global_receive(): fix IRQ storm on global FIFO receive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx. 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




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux