linux-kernel - Re: AUTOSEL process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.2303211125090.55912@angie.orcam.me.uk>
Date:   Tue, 21 Mar 2023 12:41:06 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Greg KH <greg@...ah.com>
cc:     Pavel Machek <pavel@....cz>, Willy Tarreau <w@....eu>,
        Matthew Wilcox <willy@...radead.org>,
        Eric Biggers <ebiggers@...nel.org>,
        Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, viro@...iv.linux.org.uk,
        linux-fsdevel@...r.kernel.org
Subject: Re: AUTOSEL process

On Sat, 11 Mar 2023, Greg KH wrote:

> So no, forcing a maintainer/author to ack a patch to get it into stable
> is not going to work UNLESS a maintainer/author explicitly asks for
> that, which some have, and that's wonderful.

 FWIW I'm happy to ack patches for stable backporting (and I tag patches 
of mine for stable as I deem appropriate).

  Maciej