From: Andrew Lunn <andrew@lunn.ch>
To: Byron Stanoszek <gandalf@winds.org>
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: Wed, 22 Apr 2026 14:11:24 +0200 [thread overview]
Message-ID: <41d9fe43-9aa5-49b4-89cd-9aa13e4e4ea9@lunn.ch> (raw)
In-Reply-To: <9a0bc592-fb74-f646-1752-4359c0ac31a2@polinggroup.com>
On Tue, Apr 21, 2026 at 11:03:28PM -0400, Byron Stanoszek wrote:
> 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.
Hi Byron
I will drop this driver from the patchset.
Andrew
next prev parent reply other threads:[~2026-04-22 12:11 UTC|newest]
Thread overview: 41+ 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
2026-04-22 12:11 ` Andrew Lunn [this message]
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-23 2:44 ` Jakub Kicinski
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=41d9fe43-9aa5-49b4-89cd-9aa13e4e4ea9@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gandalf@winds.org \
--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