Re: Fwd: Request to add mainline merged patch to stable kernels

[Greg KH <gregkh@linuxfoundation.org>]

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Thu, Jan 08, 2026 at 11:57:58AM +1100, JP Dehollain wrote:
> Thanks, I can do that, just note that these patches had already been
> previously submitted and merged into mainline:
> 
> 1/2 - [PATCH] misc: rtsx: Add support for RTS5264 Version B and
> optimize init flow - Ricky Wu
> Link: https://lore.kernel.org/all/20250620071325.1887017-1-ricky_wu@realtek.com/
> 
> 2/2 - [PATCH] misc: rtsx_pci: Add separate CD/WP pin polarity reversal
> support - Ricky Wu
> Link: https://lore.kernel.org/all/20250812063521.2427696-1-ricky_wu@realtek.com/
> 
> The request is to also get them merged into all previous stable
> versions.

What exactly is "all"?

And what are the git ids for these commits?

> Apologies if I'm missing some trivial context, I'm just
> learning about the kernel development process and I'm not across this
> process of porting patches across kernel versions.

The process is documented here:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

for basic stable stuff, but when you want a series backported that
doesn't apply cleanly, you need to provide a tested series yourself.

thanks,

greg k-h