On Tue, May 24, 2022 at 07:48:51PM +0200, Vegard Nossum wrote: > > On 5/24/22 17:35, Greg KH wrote: > > On Tue, May 24, 2022 at 05:27:56PM +0200, Vegard Nossum wrote: > >> > >> On 5/24/22 17:22, Greg KH wrote: > >>> What kernel tree(s) are you wanting this to be applied to? > >> > >> I replied to the v5.17 email > >> (https://lore.kernel.org/stable/165314153515625@xxxxxxxxx/T/#u) and I've > >> only tested this on top of 5.17.9. > >> > >> Is that generally enough to trigger attempts to automatically > >> cherry-pick it onto the older branches or should I test and submit for > >> the older ones as well? > > > > You should test and submit for the older ones as well please. > > Thanks, will do shortly. > > >> How would you prefer to indicate the kernel tree(s) in the future? > > > > Just say so in the [PATCH 5.17.y] subject line, or in the signed-off-by > > area or below the --- line. > > > > Responding to the email and relying on the thread alone doesn't usually > > work as the original message is long gone from my mailboxes, I can't > > keep that old stuff cluttering up the place :) > > If you want to make it easier for people to respond to these emails you > could change the FAILED: message to list specific git commands needed to > fix and submit. For this one in particular, you could for example make > it say: > > git fetch > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ > linux-5.17.y > git checkout FETCH_HEAD > git cherry-pick -x 9f46c187e2e680ecd9de7983e4d081c3391acc76 > # <resolve conflicts, build, test, etc.> > git send-email --subject-prefix 'PATCH 5.17.y' --to > 'stable@xxxxxxxxxxxxxxx' HEAD^.. > > Just an idea... That's a nice idea, I'll consider adding it to my scripts. > (And argh, just sent out for 5.15 and I put "PATCH 5.15" instead of > "PATCH 5.15.y" -- does that matter?) No, not at all, all is good and now queued up, thanks. greg k-h
