On Fri, Oct 14, 2022 at 03:55:03PM -0500, Tyler Hicks wrote:
Hey Greg and Sasha - I'm starting to think through how I can monitor for dropped stable patches that touch certain file paths in order to help out with backporting. I've come across a few examples where Greg's automated emails point out that the patch couldn't be applied to a certain series but then the patch shows up in a future -rc release without anyone submitting a fixed backport to the list. An example:
FAILED email: https://lore.kernel.org/stable/1664091338227131@kroah.com/ -rc review email: https://lore.kernel.org/stable/20221003070722.143782710@linuxfoundation.org/
Is this just a case of one of you manually doing the backports (or dependency resolution) yourselves or are folks directly sending you backports?
This isn't a problem for me, BTW. I just want to make sure that I understand the process. Thanks!
If there's nothing on the mailing list, it's usually me fixing up dropped patches.
In the example above, you can see I took an additional patch right before the one you've linked to make things work.
I think that the only exception are the occasional "security" patches that happen off list and take some time to get backported.