From: Alessio Ferri <alessio.ferri@mythread.it>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ANN] I will stop applying driver patches
Date: Fri, 6 Nov 2026 17:26:31 +0100 [thread overview]
Message-ID: <20261106172631.00002d25@mythread.it> (raw)
Hi Johannes,
in defense of the people who "send patches to decades-old drivers":
Those drivers are incomplete/buggy/a pain to deal with, usually because
of the poor vendor support or totally missing documentation (no need to
name names).
A lot of people (I am one of them) have had to deal with them for ages,
with great suffering and little hope of ever fixing the situation,
because of missing developers interested in fixing them / no
documentation to start from / no time to reverse the whole thing.
Finally today, with some assistance from an LLM, one could hope to have
working hardware with Linux, or at least try to; it seems then natural
to send patches upstream for review, instead of keeping them private.
Sometimes, even with an LLM helping, the work takes months.
Sometimes, the contributor has no idea of what they are doing, and
I get why this is a problem, after all maintainers are not review
machines.
But, there has to be a middle ground, maybe a small overall quota per
merge window would push people to self-review their own work more
carefully. That would avoid creating perverse incentives, like
forcing people to give reviews, with the risk of having people give away
random Reviewed-by tags just to reach the required number.
Best regards
Alessio
next reply other threads:[~2026-11-06 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:26 Alessio Ferri [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-05 21:27 [ANN] I will stop applying driver patches Johannes Berg
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=20261106172631.00002d25@mythread.it \
--to=alessio.ferri@mythread.it \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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