From: Finn Thain <fthain@linux-m68k.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Daniel Palmer <daniel@0x0f.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Lunn <andrew@lunn.ch>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Michael Fritscher <michael@fritscher.net>,
Byron Stanoszek <gandalf@winds.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-doc@vger.kernel.org,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH net v2 10/15] drivers: net: cirrus: mac89x0: Remove this driver
Date: Fri, 24 Apr 2026 11:04:02 +1000 (AEST) [thread overview]
Message-ID: <31926a28-658a-1df9-d5bc-2b010891e7e7@linux-m68k.org> (raw)
In-Reply-To: <20260423150240.07c350a2@kernel.org>
On Thu, 23 Apr 2026, Jakub Kicinski wrote:
> We want to be welcoming in the community. But being a part of the
> community means participating in _work_.
>
The work of testing drivers requires that maintainers have ready access to
actual hardware. Behavioural simulation like QEMU does not cut it.
Therefore, it sounds like you're going to need someone with actual clout
to mandate that drivers must have maintainers and those maintainers must
have access to working hardware, or those drivers get placed on a removal
schedule along with _every_ other orphaned module across the entire tree.
That way, you get to chase _all_ freeloaders regardless of whether they
are unpaid enthusiasts or foundation sponsors. Surely you'd find out what
"welcoming" really means -- but you would get to remove a _lot_ of code.
Far more likely, you'd find out that the typical Linux user is actually a
retro computing enthusiast because he's using some device that's over 5
years old, and the employer of the maintainer of the relevant driver got
assigned to something more profitable years ago and all their old hardware
got tossed out in the last office move. (What was that saying about those
who live in silica houses?)
Anyway, I think there is a better way. Let's score every module based on
cost/benefit to the "community". We can use retail sales volume as a proxy
for the former quantity (in unadjusted dollars) and use module size (in
lines of code) as proxy for the latter. If nothing else, that would show
us which modules are more or less valuable to the community, relative to
the average module.
next prev parent reply other threads:[~2026-04-24 1:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 18:01 [PATCH net v2 00/15] Remove a number of ISA and PCMCIA Ethernet drivers Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 01/15] drivers: net: 3com: 3c509: Remove this driver Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 02/15] drivers: net: 3com: 3c515: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 03/15] drivers: net: 3com: 3c574: " Andrew Lunn
2026-04-23 2:14 ` Wei Fang
2026-04-23 2:21 ` Jakub Kicinski
2026-04-22 18:01 ` [PATCH net v2 04/15] drivers: net: 3com: 3c589: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 05/15] drivers: net: amd: lance: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 06/15] drivers: net: amd: nmclan: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 07/15] drivers: net: smsc: smc9194: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 08/15] drivers: net: smsc: smc91c92: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 09/15] drivers: net: cirrus: cs89x0: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 10/15] drivers: net: cirrus: mac89x0: " Andrew Lunn
2026-04-23 7:07 ` Geert Uytterhoeven
2026-04-23 7:10 ` John Paul Adrian Glaubitz
2026-04-23 8:52 ` Daniel Palmer
2026-04-23 9:28 ` John Paul Adrian Glaubitz
2026-04-23 22:02 ` Jakub Kicinski
2026-04-24 1:04 ` Finn Thain [this message]
2026-04-22 18:01 ` [PATCH net v2 11/15] drivers: net: fujitsu: fmvj18x: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 12/15] drivers: net: 8390: AX88190: " Andrew Lunn
2026-04-23 9:06 ` Bjørn Mork
2026-04-22 18:01 ` [PATCH net v2 13/15] drivers: net: 8390: pcnet: " Andrew Lunn
2026-04-23 5:49 ` Dominik Brodowski
2026-04-23 12:04 ` Andrew Lunn
2026-04-23 14:01 ` Dominik Brodowski
2026-04-23 9:09 ` Bjørn Mork
2026-04-22 18:01 ` [PATCH net v2 14/15] drivers: net: 8390: ultra: " Andrew Lunn
2026-04-22 18:01 ` [PATCH net v2 15/15] drivers: net: 8390: wd80x3: " Andrew Lunn
2026-04-30 3:14 ` kernel test robot
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=31926a28-658a-1df9-d5bc-2b010891e7e7@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=daniel@0x0f.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gandalf@winds.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=michael@fritscher.net \
--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