From: Chao Yu <chao@kernel.org>
To: Yunlei He <heyunlei@oppo.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: update mtime and ctime in move file range method
Date: Mon, 26 Jun 2023 17:15:04 +0800 [thread overview]
Message-ID: <b8f06eef-5249-d08f-b4f1-800ca14d770b@kernel.org> (raw)
In-Reply-To: <20230625160627.4112651-1-heyunlei@oppo.com>
On 2023/6/26 0:06, Yunlei He wrote:
> Mtime and ctime stay old value without update after move
> file range ioctl. This patch add time update.
>
> Signed-off-by: Yunlei He <heyunlei@oppo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-06-26 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 16:06 [f2fs-dev] [PATCH 1/2 v2] f2fs: update mtime and ctime in move file range method Yunlei He via Linux-f2fs-devel
2023-06-25 16:06 ` [f2fs-dev] [PATCH 2/2 v2] f2fs: truncate pages if move file range success Yunlei He via Linux-f2fs-devel
2023-06-26 9:15 ` Chao Yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 16:16 [f2fs-dev] [PATCH 1/2 v2] f2fs: update mtime and ctime in move file range method Yunlei He via Linux-f2fs-devel
2023-06-23 1:42 ` Chao Yu
2023-06-23 18:55 ` Jaegeuk Kim
2023-06-21 9:43 Yunlei He via Linux-f2fs-devel
2023-06-21 13:39 ` Chao Yu
2023-06-22 16:23 ` 何云蕾(Yunlei he) via Linux-f2fs-devel
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=b8f06eef-5249-d08f-b4f1-800ca14d770b@kernel.org \
--to=chao@kernel.org \
--cc=heyunlei@oppo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).