Linux kernel -stable discussions
 help / color / mirror / Atom feed
* Process question about dropped patches
@ 2022-10-14 20:55 Tyler Hicks
  2022-10-15 11:24 ` Sasha Levin
  0 siblings, 1 reply; 2+ messages in thread
From: Tyler Hicks @ 2022-10-14 20:55 UTC (permalink / raw)
  To: gregkh, Sasha Levin; +Cc: stable

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!

Tyler

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Process question about dropped patches
  2022-10-14 20:55 Process question about dropped patches Tyler Hicks
@ 2022-10-15 11:24 ` Sasha Levin
  0 siblings, 0 replies; 2+ messages in thread
From: Sasha Levin @ 2022-10-15 11:24 UTC (permalink / raw)
  To: Tyler Hicks; +Cc: gregkh, stable

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.

-- 
Thanks,
Sasha

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-10-15 11:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-14 20:55 Process question about dropped patches Tyler Hicks
2022-10-15 11:24 ` Sasha Levin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox