From: Eric Biggers <ebiggers@kernel.org>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Demi Marie Obenour <demiobenour@gmail.com>,
Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] crypto: qce - Remove driver
Date: Wed, 29 Jul 2026 10:38:29 -0700 [thread overview]
Message-ID: <20260729173829.GB4454@quark> (raw)
In-Reply-To: <CAMRc=Mch_3fFqq+khutEMQG3P-ojBE2dnLy_U2_gDV4e1ro6aA@mail.gmail.com>
On Wed, Jul 29, 2026 at 05:02:08AM -0700, Bartosz Golaszewski wrote:
> On Tue, 28 Jul 2026 17:22:41 +0200, Eric Biggers <ebiggers@kernel.org> said:
> > On Fri, Jul 24, 2026 at 08:51:44AM -0700, Eric Biggers wrote:
> >> It is consuming a lot of the community's time to help maintain,
> >> including dealing with LLM-found bugs, with no clear benefit to anyone.
> >> Even considering *just today* we can see someone sent a bug fix:
> >> https://lore.kernel.org/linux-crypto/20260724081537.191992-2-thorsten.blum@linux.dev/
> >
> > Another example:
> > https://lore.kernel.org/linux-crypto/d5de5a55-eb35-4ad5-8d53-12e188e156cb@oss.qualcomm.com/
> >
> Are you seriously complaining about people sending fixes to a driver we want
> to see fixed? We don't remove maintained drivers, this has been the kernel
> policy for years. Unfortunately if we want to fix it, then it'll take some
> work involving sending patches to the mailing list.
This again completely misses the point. The point is that maintenance
is a community effort, and just because you have a M: entry (without a
git tree) doesn't mean it isn't taking time from other people too.
Now if it actually provided a benefit to users that generally would be
fine. But in reality it just causes problems (with the possible
exception of the one point raised today where the driver is "needed" to
power off the hardware, though that part is broken too).
- Eric
next prev parent reply other threads:[~2026-07-29 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260724050645.223799-1-ebiggers@kernel.org>
2026-07-24 5:28 ` [PATCH] crypto: qce - Remove driver Greg Kroah-Hartman
2026-07-24 7:36 ` Bartosz Golaszewski
2026-07-24 8:41 ` Greg Kroah-Hartman
2026-07-24 9:29 ` Bartosz Golaszewski
2026-07-24 14:14 ` Eric Biggers
2026-07-24 14:47 ` Bartosz Golaszewski
2026-07-24 15:04 ` Greg Kroah-Hartman
2026-07-24 15:09 ` Eric Biggers
2026-07-24 15:25 ` Greg Kroah-Hartman
2026-07-24 15:51 ` Eric Biggers
2026-07-27 13:26 ` Bartosz Golaszewski
2026-07-28 15:30 ` Eric Biggers
2026-07-28 15:22 ` Eric Biggers
2026-07-29 8:02 ` Konrad Dybcio
2026-07-29 14:55 ` Eric Biggers
2026-07-29 16:55 ` Konrad Dybcio
2026-07-29 17:18 ` Eric Biggers
2026-07-29 12:02 ` Bartosz Golaszewski
2026-07-29 17:38 ` Eric Biggers [this message]
[not found] ` <amM22cX7KTqyOoOk@sumit-xelite>
2026-07-24 13:51 ` Eric Biggers
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=20260729173829.GB4454@quark \
--to=ebiggers@kernel.org \
--cc=brgl@kernel.org \
--cc=demiobenour@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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