From: Christoph Hellwig <hch@infradead.org>
To: Zhang Yi <yi.zhang@huaweicloud.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, djwong@kernel.org,
hch@infradead.org, brauner@kernel.org, david@fromorbit.com,
tytso@mit.edu, jack@suse.cz, yi.zhang@huawei.com,
chengzhihao1@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter()
Date: Sun, 17 Mar 2024 18:35:34 -0700 [thread overview]
Message-ID: <ZfeaZtDqi9JVnzS8@infradead.org> (raw)
In-Reply-To: <20240315125354.2480344-9-yi.zhang@huaweicloud.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2024-03-18 1:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 12:53 [PATCH v2 00/10] xfs/iomap: fix non-atomic clone operation and don't update size when zeroing range post eof Zhang Yi
2024-03-15 12:53 ` [PATCH v2 01/10] xfs: match lock mode in xfs_buffered_write_iomap_begin() Zhang Yi
2024-03-15 12:53 ` [PATCH v2 02/10] xfs: allow xfs_bmapi_convert_delalloc() to pass NULL seq Zhang Yi
2024-03-18 1:28 ` Christoph Hellwig
2024-03-18 6:36 ` Zhang Yi
2024-03-15 12:53 ` [PATCH v2 03/10] xfs: make xfs_bmapi_convert_delalloc() to allocate the target offset Zhang Yi
2024-03-18 1:29 ` Christoph Hellwig
2024-03-15 12:53 ` [PATCH v2 04/10] xfs: drop xfs_convert_blocks() Zhang Yi
2024-03-18 1:33 ` Christoph Hellwig
2024-03-18 6:38 ` Zhang Yi
2024-03-15 12:53 ` [PATCH v2 05/10] xfs: convert delayed extents to unwritten when zeroing post eof blocks Zhang Yi
2024-03-18 1:34 ` Christoph Hellwig
2024-03-15 12:53 ` [PATCH v2 06/10] iomap: drop the write failure handles when unsharing and zeroing Zhang Yi
2024-03-18 1:34 ` Christoph Hellwig
2024-03-15 12:53 ` [PATCH v2 07/10] iomap: don't increase i_size if it's not a write operation Zhang Yi
2024-03-18 1:35 ` Christoph Hellwig
2024-03-15 12:53 ` [PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter() Zhang Yi
2024-03-18 1:35 ` Christoph Hellwig [this message]
2024-03-15 12:53 ` [PATCH v2 09/10] iomap: make block_write_end() return a boolean Zhang Yi
2024-03-18 1:36 ` Christoph Hellwig
2024-03-15 12:53 ` [PATCH v2 10/10] iomap: do some small logical cleanup in buffered write Zhang Yi
2024-03-18 1:37 ` Christoph Hellwig
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=ZfeaZtDqi9JVnzS8@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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