From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Documenting the correct pushback on AI inspired (and other) fixes in older drivers
Date: Thu, 05 Feb 2026 22:40:12 +0000 [thread overview]
Message-ID: <5cfff8c0b44968cf75d74aef17de6dce73e1a26d.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAJpMwyg4Etv3qOw2Ur+L9YmWbt7Rw19uTs0=RsRtuORaEOoHnQ@mail.gmail.com>
On Thu, 2026-02-05 at 17:40 +0100, Haris Iqbal wrote:
[...]
> It is an interesting proposal, but I feel the problem statement
> overlaps with some other, already being discussed, or covered topics.
> For example, the topic of fixes requiring effort and time of the
> maintainer/reviewer, and the fact that AI now potentially leads to
> too many such fixes is being discussed in the following link,
>
> https://lore.kernel.org/ksummit/20251114183528.1239900-1-dave.hansen@linux.intel.com/#t
They are actually pretty orthogonal. The email is about identifying AI
tools used in submission. I may suspect the uptick in the fixes is due
to the use of AI, but I don't really care. The problem isn't what tool
you used it's that the risk vs benefit of actually fixing the driver
isn't favourable.
Regards,
James
next prev parent reply other threads:[~2026-02-05 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 9:51 [LSF/MM/BPF TOPIC] Documenting the correct pushback on AI inspired (and other) fixes in older drivers James Bottomley
2026-02-05 16:30 ` Bart Van Assche
2026-02-05 20:54 ` Matthew Wilcox
2026-02-05 22:38 ` James Bottomley
2026-02-05 16:40 ` Haris Iqbal
2026-02-05 22:40 ` James Bottomley [this message]
2026-02-05 23:37 ` Chuck Lever
2026-02-05 22:57 ` Finn Thain
2026-02-06 5:18 ` Darrick J. Wong
2026-02-06 22:38 ` Finn Thain
2026-02-08 17:58 ` James Bottomley
2026-02-08 23:41 ` 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=5cfff8c0b44968cf75d74aef17de6dce73e1a26d.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=haris.iqbal@ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@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