From: Byron Stanoszek <gandalf@winds.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net 00/18] Remove a number of ISA and PCMCIA Ethernet drivers
Date: Tue, 21 Apr 2026 23:03:28 -0400 (EDT) [thread overview]
Message-ID: <9a0bc592-fb74-f646-1752-4359c0ac31a2@polinggroup.com> (raw)
In-Reply-To: <e056d348-4560-4df3-85c4-e29393b004e9@lunn.ch>
On Wed, 22 Apr 2026, Andrew Lunn wrote:
>
> Could you live with v6.18, which has an expected EOL of December 2028?
> If you are only updating once per year, security is not an issue, you
> just want stability.
I could for the time being, but this hasn't worked for me in the past. Usually
what happens is the PC breaks down, and the customer swaps in a new
backplane+SBC and moves all their PCI cards over. I then find I need to update
the kernel just to get the Intel DRM to work properly on the new CPU. Some of
these systems were installed back in the Linux 2.6 era, so I've gone through
several "Intel DRM not working" steps ever since CPUs started getting
integrated graphics. 2028 will come fast.
One thing worth mentioning though--these 3com cards are all PCI. They still
work perfectly fine on the newest hardware. Your subject says you're dropping
old ISA and PCMCIA support, so I don't fully understand why you included 3c59x
in the mix. Phoronix picked up this patch
(https://www.phoronix.com/news/Linux-Old-Network-AI), and according to the
comments, there are still people who use these cards (3c905s were very popular
back in the day). Would you be willing to leave this driver in mainline?
> However, just because a driver has gone from HEAD, it does not really
> prevent us from taking patches for stable. But we Maintainers want to
> avoid doing the triage work, figuring out good from bad.
>
> We have not discussed it as a Maintainer team, but one thing which
> might work is we add a entry for 3c59x.c in MAINTAINERS, in stable,
> pointing to you. You can then validate patches, and tell us if they
> are O.K. to queue for stable.
I'm sorry, but I already have enough going on to take up another maintainer
role. However, I thought Greg had some rule in place that said the stable
branches don't get any patches applied unless they also hit mainline. Is there
some exception for drivers in stable that don't exist in mainline anymore?
Thanks,
-Byron
next prev parent reply other threads:[~2026-04-22 3:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 19:31 [PATCH net 00/18] Remove a number of ISA and PCMCIA Ethernet drivers Andrew Lunn
2026-04-21 19:31 ` [PATCH net 01/18] drivers: net: 3com: 3c509: Remove this driver Andrew Lunn
2026-04-21 19:31 ` [PATCH net 02/18] drivers: net: 3com: 3c515: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 03/18] drivers: net: 3com: 3c574: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 04/18] drivers: net: 3com: 3c589: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 05/18] drivers: net: 3com: 3c59x: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 06/18] drivers: net: amd: Remove hplance and mvme147 Andrew Lunn
2026-04-21 21:38 ` Daniel Palmer
2026-04-22 12:50 ` Andrew Lunn
2026-04-22 7:37 ` Geert Uytterhoeven
2026-04-21 19:31 ` [PATCH net 07/18] drivers: net: amd: lance: Remove this driver Andrew Lunn
2026-04-21 19:31 ` [PATCH net 08/18] drivers: net: amd: nmclan: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 09/18] drivers: net: smsc: smc9194: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 10/18] drivers: net: smsc: smc91c92: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 11/18] drivers: net: cirrus: cs89x0: " Andrew Lunn
2026-04-22 7:31 ` Geert Uytterhoeven
2026-04-22 12:13 ` Andrew Lunn
2026-04-22 12:17 ` Geert Uytterhoeven
2026-04-21 19:31 ` [PATCH net 12/18] drivers: net: cirrus: mac89x0: " Andrew Lunn
2026-04-21 21:34 ` Daniel Palmer
2026-04-22 7:36 ` Geert Uytterhoeven
2026-04-21 19:31 ` [PATCH net 13/18] drivers: net: fujitsu: fmvj18x: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 14/18] drivers: net: xircom: xirc2ps: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 15/18] drivers: net: 8390: AX88190: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 16/18] drivers: net: 8390: pcnet: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 17/18] drivers: net: 8390: ultra: " Andrew Lunn
2026-04-21 19:31 ` [PATCH net 18/18] drivers: net: 8390: wd80x3: " Andrew Lunn
2026-04-21 19:53 ` [PATCH net 00/18] Remove a number of ISA and PCMCIA Ethernet drivers Andrew Lunn
2026-04-22 1:39 ` Jakub Kicinski
2026-04-21 20:44 ` Byron Stanoszek
2026-04-21 22:30 ` Andrew Lunn
2026-04-22 3:03 ` Byron Stanoszek [this message]
2026-04-22 12:11 ` Andrew Lunn
2026-04-22 15:19 ` Byron Stanoszek
2026-04-21 22:03 ` Daniel Palmer
2026-04-22 9:13 ` David Laight
2026-04-22 9:33 ` Daniel Palmer
2026-04-22 5:42 ` John Paul Adrian Glaubitz
2026-04-22 7:42 ` Geert Uytterhoeven
2026-04-22 10:45 ` Finn Thain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a0bc592-fb74-f646-1752-4359c0ac31a2@polinggroup.com \
--to=gandalf@winds.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox