Linux filesystem development
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Theodore Tso <tytso@mit.edu>, Christoph Hellwig <hch@lst.de>,
	Carlos Maiolino <cem@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Joanne Koong <joannelkoong@gmail.com>,
	changfengnan@bytedance.com,
	Christian Brauner <brauner@kernel.org>,
	linux-ext4@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: selective Sashiko replies, was: Re: [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw
Date: Tue, 28 Jul 2026 10:46:52 -0700	[thread overview]
Message-ID: <20260728104652.719d23d0@kernel.org> (raw)
In-Reply-To: <87h5ljf2h2.fsf@trenco.lwn.net>

On Tue, 28 Jul 2026 11:28:25 -0600 Jonathan Corbet wrote:
> > On Tue, Jul 28, 2026 at 07:27:56AM -0500, Jakub Kicinski wrote:  
> >> 
> >> +1, maybe perhaps someone wants the off-list option, dunno. 
> >> But trimming the CC list of the on-list reply is a really weird idea.
> >> Submissions often CC multiple vger lists, and the bot only replies to one.  
> >
> > It's not (necessarily) "just one" mailing list.
> >
> > For better or for worse, there are people who have claimed that being
> > exposed to LLM reviews would "deman their humanity".  
> 
> Can I offer a slightly different perspective here?  I am not one of the
> people who has said such things about LLM reviews, but I perhaps
> understand at least part of where they are coming from.  It's not "being
> exposed" to reviews that is demeaning, it is being forced to justify
> one's work to a machine.

FWIW I think that's an entirely reasonable concern, and some people do
indeed get irritated having to fight the AI slop reviews.

I thought the complaint was about the cases where the author is notified
about the review, and so is at least one ML. But the CC list is cut
down, so that a human reviewer doesn't see the AI output. They find 
the same issue as the AI. And then the author responds with "AI already
told me: $lore-link". Which is really maximizing everyone's misery.

  reply	other threads:[~2026-07-28 17:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 12:49 decouple simple direct I/O reads from iomap_dio_rw Christoph Hellwig
2026-07-22 12:49 ` [PATCH 1/3] iomap: split iomap_iter() logic into iomap_iter_next() Christoph Hellwig
2026-07-23  2:06   ` changfengnan
2026-07-22 12:49 ` [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw Christoph Hellwig
2026-07-22 19:03   ` Joanne Koong
2026-07-23  2:17     ` changfengnan
2026-07-23  4:55       ` Christoph Hellwig
2026-07-23  4:53     ` Christoph Hellwig
2026-07-23 15:10       ` Darrick J. Wong
2026-07-23 16:08         ` Theodore Tso
2026-07-24 12:47           ` Carlos Maiolino
2026-07-28  4:01             ` selective Sashiko replies, was: " Christoph Hellwig
2026-07-28 14:27               ` Jakub Kicinski
2026-07-28 14:42                 ` Theodore Tso
2026-07-28 17:28                   ` Jonathan Corbet
2026-07-28 17:46                     ` Jakub Kicinski [this message]
2026-07-22 12:49 ` [PATCH 3/3] iomap: use GFP_NOWAIT when application for iomap_dio_simple allocations Christoph Hellwig
2026-07-22 21:01   ` Joanne Koong
2026-07-23  2:06     ` changfengnan

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=20260728104652.719d23d0@kernel.org \
    --to=kuba@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=changfengnan@bytedance.com \
    --cc=corbet@lwn.net \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=joannelkoong@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=workflows@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