Re: [PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter()
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: Zhang Yi <yi.zhang@xxxxxxxxxxxxxxx>
Subject
: Re: [PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter()
From
: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date
: Sun, 17 Mar 2024 18:35:34 -0700
Cc
: linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, djwong@xxxxxxxxxx, hch@xxxxxxxxxxxxx, brauner@xxxxxxxxxx, david@xxxxxxxxxxxxx, tytso@xxxxxxx, jack@xxxxxxx, yi.zhang@xxxxxxxxxx, chengzhihao1@xxxxxxxxxx, yukuai3@xxxxxxxxxx
In-reply-to
: <
20240315125354.2480344-9-yi.zhang@huaweicloud.com
>
Looks good: Reviewed-by: Christoph Hellwig <hch@xxxxxx>
References
:
[PATCH v2 00/10] xfs/iomap: fix non-atomic clone operation and don't update size when zeroing range post eof
From:
Zhang Yi
[PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter()
From:
Zhang Yi
Prev by Date:
Re: [PATCH v2 07/10] iomap: don't increase i_size if it's not a write operation
Next by Date:
Re: [PATCH v2 09/10] iomap: make block_write_end() return a boolean
Previous by thread:
[PATCH v2 08/10] iomap: use a new variable to handle the written bytes in iomap_write_iter()
Next by thread:
[PATCH v2 10/10] iomap: do some small logical cleanup in buffered write
Index(es):
Date
Thread
[Index of Archives]
[Linux Ext4 Filesystem]
[Union Filesystem]
[Filesystem Testing]
[Ceph Users]
[Ecryptfs]
[NTFS 3]
[AutoFS]
[Kernel Newbies]
[Share Photos]
[Security]
[Netfilter]
[Bugtraq]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux Cachefs]
[Reiser Filesystem]
[Linux RAID]
[NTFS 3]
[Samba]
[Device Mapper]
[CEPH Development]