All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Theodore Tso <tytso@mit.edu>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	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: selective Sashiko replies, was: Re: [PATCH 2/3] iomap: decouple simple direct I/O reads from iomap_dio_rw
Date: Tue, 28 Jul 2026 06:01:20 +0200	[thread overview]
Message-ID: <20260728040120.GA19400@lst.de> (raw)
In-Reply-To: <amNerp4LwjSkHS5t@andromeda.toxiclabs.cc>

On Fri, Jul 24, 2026 at 02:47:58PM +0200, Carlos Maiolino wrote:
> > Whether or not the review goes to a mailing list is up to each
> > subsystem to determine.  Some people have violently objected to the
> > review going to the mailing list, which is why it's optional.
> > 
> > I have asked to have ext4 reviews to be cc'ed to the linux-ext4
> > list[1].  It would be up to the VFS maintainers whether or not we want
> > to enable it for linux-fsdevel.
> > 
> > [1] https://github.com/sashiko-dev/sashiko/pull/365
> > 
> > The XFS maintainers can request if patches cc'ed to linux-fs should
> > get reviewed and sent back to authors and/or the maintainers and/or
> > the linux-fs mailing list.  You can either ask the Sashiko devs to
> > edit the email_policy.toml file, or you can send a pull request yourself.
> > 
> 
> IIRC the discussion we had a while back was to keep the reviews emailed
> to authors only...
> 
> Now I wonder how feasible would be to have a "linux-xfs-review" list to
> send sashiko reviews to, then people opt-in to it? Would it be overkill?

The main problem is that reducing the recipient list for replies is
incredibly stupid.  You can do that for a private offlist conversion
on something sensitive, but not by default.  If I get a reply, it needs
to go everywhere.  I have to admit I find the sashiko replies a lot
less useful than the web interface, but the important bit is to be
consistent.

  reply	other threads:[~2026-07-28  4:01 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             ` Christoph Hellwig [this message]
2026-07-28 14:27               ` selective Sashiko replies, was: " Jakub Kicinski
2026-07-28 14:42                 ` Theodore Tso
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=20260728040120.GA19400@lst.de \
    --to=hch@lst.de \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=changfengnan@bytedance.com \
    --cc=djwong@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.