From: Chao Yu <chao@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
"Fabio M . De Francesco" <fmdefrancesco@gmail.com>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: use memcpy_{to, from}_page() where possible
Date: Sat, 20 Aug 2022 10:39:34 +0800 [thread overview]
Message-ID: <a2e3faf6-dedc-7ee7-0b08-8a5f2bfc2d25@kernel.org> (raw)
In-Reply-To: <20220819223300.9128-1-ebiggers@kernel.org>
On 2022/8/20 6:33, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> This is simpler, and as a side effect it replaces several uses of
> kmap_atomic() with its recommended replacement kmap_local_page().
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2022-08-20 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 22:33 [PATCH v2] f2fs: use memcpy_{to,from}_page() where possible Eric Biggers
2022-08-20 2:08 ` Fabio M. De Francesco
2022-08-20 2:39 ` 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=a2e3faf6-dedc-7ee7-0b08-8a5f2bfc2d25@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fmdefrancesco@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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).