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] f2fs: remove unneeded page uptodate check/set
Date: Tue, 20 Jun 2023 17:20:03 +0800 [thread overview]
Message-ID: <a6b7bd99-cd2c-69ef-a021-29a4baf7569d@kernel.org> (raw)
In-Reply-To: <20230619151353.2168306-1-heyunlei@oppo.com>
On 2023/6/19 23:13, Yunlei He wrote:
> This patch remove unneeded page uptodate check/set in
> f2fs_vm_page_mkwrite, which already done in set_page_dirty.
>
> 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
prev parent reply other threads:[~2023-06-20 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 15:13 [f2fs-dev] [PATCH] f2fs: remove unneeded page uptodate check/set Yunlei He via Linux-f2fs-devel
2023-06-20 9:20 ` Chao Yu [this message]
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=a6b7bd99-cd2c-69ef-a021-29a4baf7569d@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).