From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, jack@suse.cz, djwong@kernel.org
Subject: Re: [PATCH RFC 1/2] iomap: prioritize iter.status error over ->iomap_end()
Date: Tue, 2 Sep 2025 23:09:51 -0700 [thread overview]
Message-ID: <aLfbr-LpArXGuNS5@infradead.org> (raw)
In-Reply-To: <20250902150755.289469-2-bfoster@redhat.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-09-03 6:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 15:07 [PATCH RFC 0/2] iomap: ->iomap_end() error handling fixes Brian Foster
2025-09-02 15:07 ` [PATCH RFC 1/2] iomap: prioritize iter.status error over ->iomap_end() Brian Foster
2025-09-03 6:09 ` Christoph Hellwig [this message]
2025-09-03 11:04 ` Jan Kara
2025-09-06 4:23 ` Ritesh Harjani
2025-09-02 15:07 ` [PATCH RFC 2/2] iomap: revert the iomap_iter pos on ->iomap_end() error Brian Foster
2025-09-02 21:11 ` Joanne Koong
2025-09-03 12:18 ` Brian Foster
2025-09-03 18:31 ` Joanne Koong
2025-09-03 13:38 ` Jan Kara
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=aLfbr-LpArXGuNS5@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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