[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y05+51lztI5yi/A6@shell.armlinux.org.uk>
Date: Tue, 18 Oct 2022 11:24:39 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Pavel Machek <pavel@...x.de>
Cc: Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
andrew@...n.ch, hkallweit1@...il.com, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.10 21/34] net: sfp: move Alcatel Lucent
3FE46541AA fixup
On Tue, Oct 18, 2022 at 11:43:32AM +0200, Pavel Machek wrote:
> Hi!
>
> > Add a new fixup mechanism to the SFP quirks, and use it for this
> > module.
>
> There are two preparation patches for this, but this does not fix
> anything -- it just reimplement quirk in a different way.
>
> We should not have patches 19-21 in stable.
They should be being dropped as, as a result of this ongoing madness,
I've requested stable to no longer consider *any* of my patches for
AUTOSEL treatment.
I'm afraid that the stable kernel is loosing its purpose, and is
becoming just another development tree as long as this autosel
process exists that picks up what are development patches - coupled
with the "if you don't respond we're adding it to stable anyway"
approach means that it's a hell of a lot of work for maintainers to
be watching what stable is doing 24 hours a day 365 days a year with
_no_ possibility of having a break from that.
As I understand it, the autosel stuff is using an AI to work out
whether the patch is suitable or not, and no one bothers to look at
the quality of its selection - that task is loaded on to each
maintainer and requires said maintainer to never take any time off
from that task.
It's madness.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists