All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: brauner@kernel.org, hch@lst.de, djwong@kernel.org,
	willy@infradead.org, hsiangkao@linux.alibaba.com,
	linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 00/18] iomap: convert to in-iter iomap_next() model
Date: Thu, 2 Jul 2026 06:49:27 -0700	[thread overview]
Message-ID: <akZsZ2KV_-jsNZl9@infradead.org> (raw)
In-Reply-To: <20260701000949.1666714-1-joannelkoong@gmail.com>

What tree does this apply to?  I tried 7.2-rc1, Linus current
master, vfs/vfs.fixes and had slightly different failures to apply
with each one.

On Tue, Jun 30, 2026 at 05:09:15PM -0700, Joanne Koong wrote:
> This series implements a suggestion by Christoph for finishing the conversion
> of iomap to an iterator model. This revives Matthew's previous RFC [1], which
> had the same intention.

Btw, this evolved from my original suggestion to something that actually
looks much better, so don't give me too much credit :)


  parent reply	other threads:[~2026-07-02 13:49 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  0:09 [PATCH v2 00/18] iomap: convert to in-iter iomap_next() model Joanne Koong
2026-07-01  0:09 ` [PATCH v2 01/18] iomap: add ->iomap_next() and iomap_process() helper Joanne Koong
2026-07-02 14:00   ` Christoph Hellwig
2026-07-02 23:01     ` Joanne Koong
2026-07-02 16:23   ` Darrick J. Wong
2026-07-02 22:41     ` Joanne Koong
2026-07-01  0:09 ` [PATCH v2 02/18] xfs: convert iomap ops to ->iomap_next() Joanne Koong
2026-07-02 14:03   ` Christoph Hellwig
2026-07-02 16:48     ` Darrick J. Wong
2026-07-03 12:33       ` Christoph Hellwig
2026-07-03 15:50         ` Darrick J. Wong
2026-07-02 16:43   ` Darrick J. Wong
2026-07-02 23:59     ` Joanne Koong
2026-07-03  1:21       ` Joanne Koong
2026-07-03  1:41         ` Darrick J. Wong
2026-07-03 12:32         ` Christoph Hellwig
2026-07-03  1:38       ` Darrick J. Wong
2026-07-01  0:09 ` [PATCH v2 03/18] btrfs: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 04/18] ntfs3: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 05/18] ntfs: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 06/18] ext4: " Joanne Koong
2026-07-01 10:01   ` Jan Kara
2026-07-01  0:09 ` [PATCH v2 07/18] erofs: " Joanne Koong
2026-07-01  0:41   ` Gao Xiang
2026-07-01  0:09 ` [PATCH v2 08/18] zonefs: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 09/18] ext2: " Joanne Koong
2026-07-01 10:02   ` Jan Kara
2026-07-01  0:09 ` [PATCH v2 10/18] block: " Joanne Koong
2026-07-01  0:55   ` Keith Busch
2026-07-02 14:03     ` Christoph Hellwig
2026-07-03  0:06     ` Joanne Koong
2026-07-01  0:09 ` [PATCH v2 11/18] f2fs: " Joanne Koong
2026-07-01  0:09   ` [f2fs-dev] " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 12/18] gfs2: " Joanne Koong
2026-07-03 11:45   ` Andreas Gruenbacher
2026-07-04  0:07     ` Joanne Koong
2026-07-01  0:09 ` [PATCH v2 13/18] hpfs: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 14/18] fuse: " Joanne Koong
2026-07-01  0:09 ` [PATCH v2 15/18] exfat: " Joanne Koong
2026-07-03  1:41   ` Joanne Koong
2026-07-01  0:09 ` [PATCH v2 16/18] iomap: remove ->iomap_begin()/->iomap_end() legacy path Joanne Koong
2026-07-02 14:04   ` Christoph Hellwig
2026-07-02 16:51   ` Darrick J. Wong
2026-07-01  0:09 ` [PATCH v2 17/18] iomap: pass iomap_next_fn directly instead of struct iomap_ops Joanne Koong
2026-07-01  0:09   ` [f2fs-dev] " Joanne Koong
2026-07-01 10:04   ` Jan Kara
2026-07-01 10:04     ` [f2fs-dev] " Jan Kara
2026-07-02 14:07   ` Christoph Hellwig
2026-07-02 14:07     ` [f2fs-dev] " Christoph Hellwig
2026-07-02 16:51     ` Darrick J. Wong
2026-07-02 16:51       ` [f2fs-dev] " Darrick J. Wong via Linux-f2fs-devel
2026-07-03  1:47       ` Joanne Koong
2026-07-03  1:47         ` [f2fs-dev] " Joanne Koong
2026-07-03  2:01         ` Darrick J. Wong via Linux-f2fs-devel
2026-07-03  2:01           ` Darrick J. Wong
2026-07-03 10:37         ` Christian Brauner
2026-07-03 10:37           ` [f2fs-dev] " Christian Brauner via Linux-f2fs-devel
2026-07-02 16:58   ` Darrick J. Wong
2026-07-02 16:58     ` [f2fs-dev] " Darrick J. Wong via Linux-f2fs-devel
2026-07-03  0:17     ` Joanne Koong
2026-07-03  0:17       ` [f2fs-dev] " Joanne Koong
2026-07-03  1:42       ` Darrick J. Wong
2026-07-03  1:42         ` [f2fs-dev] " Darrick J. Wong via Linux-f2fs-devel
2026-07-01  0:09 ` [PATCH v2 18/18] Documentation: iomap: update docs to reflect iomap_next model Joanne Koong
2026-07-02 14:07   ` Christoph Hellwig
2026-07-02 19:26   ` Darrick J. Wong
2026-07-03  1:36     ` Joanne Koong
2026-07-03  2:00       ` Darrick J. Wong
2026-07-03 12:43         ` Christoph Hellwig
2026-07-03 16:11           ` Darrick J. Wong
2026-07-04  0:34             ` Joanne Koong
2026-07-04  4:38               ` Darrick J. Wong
2026-07-06  4:59                 ` Christoph Hellwig
2026-07-06  3:59               ` Christoph Hellwig
2026-07-06  3:56             ` Christoph Hellwig
2026-07-02 13:49 ` Christoph Hellwig [this message]
2026-07-03  1:08   ` [PATCH v2 00/18] iomap: convert to in-iter iomap_next() model Joanne Koong

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=akZsZ2KV_-jsNZl9@infradead.org \
    --to=hch@infradead.org \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=willy@infradead.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.