From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: introduce data read/write showing path info
Date: Tue, 29 Mar 2022 22:23:30 +0800 [thread overview]
Message-ID: <101f4cb6-37bf-0ac3-3838-7aab7e648352@kernel.org> (raw)
In-Reply-To: <YkJ5anzBIyQkiHfU@google.com>
On 2022/3/29 11:13, Jaegeuk Kim wrote:
> This was used in Android for a long time. Let's upstream it.
Could you please explain more about its usage?
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
The code part looks clean.
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2022-03-29 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 22:33 [PATCH] f2fs: introduce data read/write showing path info Jaegeuk Kim
2022-03-21 22:41 ` [f2fs-dev] " Eric Biggers
2022-03-22 0:14 ` Jaegeuk Kim
2022-03-22 0:13 ` [PATCH v2] " Jaegeuk Kim
2022-03-29 3:04 ` [f2fs-dev] " Chao Yu
2022-03-29 3:13 ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2022-03-29 14:23 ` Chao Yu [this message]
2022-03-29 18:09 ` Jaegeuk Kim
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=101f4cb6-37bf-0ac3-3838-7aab7e648352@kernel.org \
--to=chao@kernel.org \
--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