From: Matthew Wilcox <willy@infradead.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
"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, 5 Feb 2026 20:54:39 +0000 [thread overview]
Message-ID: <aYUDj5zge6amIkTv@casper.infradead.org> (raw)
In-Reply-To: <8075dab2-49db-408e-bff6-5de6b0b372cd@acm.org>
On Thu, Feb 05, 2026 at 08:30:53AM -0800, Bart Van Assche wrote:
> We don't want to forbid tree-wide API changes, isn't it? See also
> Documentation/process/stable-api-nonsense.rst.
That's plainly not what James was talking about. Tree-wide API changes
have an obvious benefit (... or if not, they'll be rejected). The
question is what benefit does anyone receive from fixing an unlikely
memory leak in the ncr53c8xx driver?
next prev parent reply other threads:[~2026-02-05 20:54 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 [this message]
2026-02-05 22:38 ` James Bottomley
2026-02-05 16:40 ` Haris Iqbal
2026-02-05 22:40 ` James Bottomley
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=aYUDj5zge6amIkTv@casper.infradead.org \
--to=willy@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bvanassche@acm.org \
--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