linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
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 2/2] f2fs: truncate pages if move file range success
Date: Wed, 21 Jun 2023 21:41:10 +0800	[thread overview]
Message-ID: <421c602b-9838-a9b4-1b7d-59d169825c52@kernel.org> (raw)
In-Reply-To: <20230621094359.3827832-2-heyunlei@oppo.com>

On 2023/6/21 17:43, Yunlei He wrote:
> If move file range success, it should remove old data from
> src and dst page cache.
> 
> 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

  reply	other threads:[~2023-06-21 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  9:43 [f2fs-dev] [PATCH 1/2 v2] f2fs: update mtime and ctime in move file range method Yunlei He via Linux-f2fs-devel
2023-06-21  9:43 ` [f2fs-dev] [PATCH 2/2] f2fs: truncate pages if move file range success Yunlei He via Linux-f2fs-devel
2023-06-21 13:41   ` Chao Yu [this message]
2023-06-21 13:39 ` [f2fs-dev] [PATCH 1/2 v2] f2fs: update mtime and ctime in move file range method Chao Yu
2023-06-22 16:23   ` 何云蕾(Yunlei he) via Linux-f2fs-devel
  -- strict thread matches above, loose matches on Subject: below --
2023-06-22 16:16 Yunlei He via Linux-f2fs-devel
2023-06-22 16:16 ` [f2fs-dev] [PATCH 2/2] f2fs: truncate pages if move file range success Yunlei He via Linux-f2fs-devel
2023-06-23  1:42   ` Chao Yu

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=421c602b-9838-a9b4-1b7d-59d169825c52@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).