Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     Arnd Bergmann <arnd@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "# 3.4.x" <stable@vger.kernel.org>,
        Lukas Hannen <lukas.hannen@opensource.tttech-industrial.com>
Subject: Re: [PATCH 5.14 298/334] time: Handle negative seconds correctly in
 timespec64_to_ns()
In-Reply-To: <YUSyKQwdpfSTbQ4H@kroah.com>
References: <20210913131113.390368911@linuxfoundation.org>
 <20210913131123.500712780@linuxfoundation.org>
 <CAK8P3a0z5jE=Z3Ps5bFTCFT7CHZR1JQ8VhdntDJAfsUxSPCcEw@mail.gmail.com>
 <874kak9moe.ffs@tglx> <YURQ4ZFDJ8E9MJZM@kroah.com> <87sfy38p1o.ffs@tglx>
 <YUSyKQwdpfSTbQ4H@kroah.com>
Date:   Fri, 17 Sep 2021 21:29:32 +0200
Message-ID: <87ee9n80gz.ffs@tglx>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Greg,

On Fri, Sep 17 2021 at 17:20, Greg Kroah-Hartman wrote:
> On Fri, Sep 17, 2021 at 12:38:43PM +0200, Thomas Gleixner wrote:
>> Nah. I try to pay more attention. I'm not against AUTOSEL per se, but
>> could we change the rules slightly?
>> 
>> Any change which is selected by AUTOSEL and lacks a Cc: stable@... is
>> put on hold until acked by the maintainer unless it is a prerequisite
>> for applying a stable tagged fix?
>> 
>> This can be default off and made effective on maintainer request.
>> 
>> Hmm?
>
> The whole point of the AUTOSEL patches are for the huge numbers of
> subsystems where maintainers and developers do not care about the stable
> trees at all, and so they do not mark patches to be backported.  So
> requireing an opt-in like this would defeat the purpose.
>
> We do allow the ability to take files/subsystems out of the AUTOSEL
> process as there are many maintainers that do do this right and get
> annoyed when patches are picked that they feel shouldn't have.  That's
> the best thing we can do for stuff like this.

I guess I was not able to express myself correctly. What I wanted to say
is:

  1) Default is AUTOSEL

  2) Maintainer can take files/subsystems out of AUTOSEL completely

     Exists today

  3) 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?

Thanks,

        tglx