Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Theodore Tso" <tytso@mit.edu>
To: Jakub Kicinski <kuba@kernel.org>
Cc: 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:42:32 -0400	[thread overview]
Message-ID: <ami9NUgcJvr0zHuk@mit.edu> (raw)
In-Reply-To: <20260728072756.7ddc9fdd@kernel.org>

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".  So the Sashiko
maintainers have made it completely up to each subsystem whether (a)
Sashiko should review the patch aat all or (b) whether the review
should be sent via e-mail, or just left on sashiko.dev web site.

If it is sent via e-mail, then who it should be sent to can be
configured to send it to the patch author (or not), or what e-mail
addresses should be sent if the patch is qualified as relevant for a
particular subsystem.  This could just be the maintainer(s), or to the
subsystem mailing list, etc.  If a patch is relevant to (say) both the
SCSI subsystem and the s390 subsystem, then it will be sent to both
subsystem mailing lists.  So it's not that the bot only replies to one
list, but only to those lists that the subsystem maintainers have
authorized.

At some level, the Sashiko developers effectively have tossed the hot
potato policy decision to the subsystem maintainers.  Given the
megathead on the ksummit mailing lsit, I can't really blame Roman for
choosing to do this ---- although I'll note the Intel zero-day bot
folks chose differently; I guess automated benchmarks aren't perceived
to demean the humanity of developers as much as LLM reviews, and so
aren't as controversial.

Cheers,

						- Ted

  reply	other threads:[~2026-07-28 14:44 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 [this message]
2026-07-28 17:28                   ` Jonathan Corbet
2026-07-28 17:46                     ` Jakub Kicinski
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=ami9NUgcJvr0zHuk@mit.edu \
    --to=tytso@mit.edu \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=changfengnan@bytedance.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=joannelkoong@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --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