On Tue, Sep 21 2021 at 15:20, Sasha Levin wrote:
On Mon, Sep 20, 2021 at 10:31:08AM -0400, Sasha Levin wrote:
On Sat, Sep 18, 2021 at 05:46:57PM +0200, Greg Kroah-Hartman wrote:
On Fri, Sep 17, 2021 at 09:29:32PM +0200, Thomas Gleixner wrote:
I guess I was not able to express myself correctly. What I wanted to say is:
Default is AUTOSEL
Maintainer can take files/subsystems out of AUTOSEL completely
Exists today
Maintainer allows AUTOSEL, but anything picked from files/subsystems without a stable tag requires an explicit ACK from the maintainer for the backport.
Is new and I would be the first to opt-in :)
My rationale for #3 is that even when being careful about stable tags, it happens that one is missing. Occasionaly AUTOSEL finds one of those in my subsystems which I appreciate.
Does that make more sense now?
Ah, yes, that makes much more sense, sorry for the confusion.
Sasha, what do you think? You are the one that scripts all of this, not me :)
I could give it a go. It adds some complexity here but is probably worth it to avoid issues.
Let me think about the best way to go about it.
So I'm thinking of yet another patch series that would go out, but instead of AUTOSEL it'll be tagged with "MANUALSEL". It would work the exact same way as AUTOSEL, without the final step of queueing up the commits into the stable trees.
Thomas, do you want to give it a go? Want to describe how I filter for commits you'd be taking care of? In the past I'd grep a combo of paths and committers (i.e. net/ && davem@), but you have your hands in too many things :)
Indeed. :(
So pretty much all what matches in MAINTAINERS entries where my name happened to end up for some reasons. That would be a good start.
Might be a bit overbroad as it also includes x86/kvm, x86/xen, x86/pci which I'm not that involved with, but to make it simple for you, I just volunteered the relevant maintainers (CCed) to participate in that experiment. :)
Thanks,
tglx