From: Chao Yu <yuchao0@huawei.com>
To: Jack Qiu <jack.qiu@huawei.com>, <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 3/3] f2fs: inline: fix wrong inline inode stat
Date: Mon, 7 Dec 2020 15:18:33 +0800 [thread overview]
Message-ID: <3f26303f-a942-77f2-fa1b-92302c08a022@huawei.com> (raw)
In-Reply-To: <20201205074055.31574-4-jack.qiu@huawei.com>
On 2020/12/5 15:40, Jack Qiu wrote:
> Miss to stat inline inode in f2fs_recover_inline_data.
>
> Signed-off-by: Jack Qiu <jack.qiu@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
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:[~2020-12-07 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 7:40 [f2fs-dev] [PATCH 0/3] f2fs: inline: fix minor bugs in f2fs_recover_inline_data Jack Qiu
2020-12-05 7:40 ` [f2fs-dev] [PATCH 1/3] f2fs: inline: correct comment " Jack Qiu
2020-12-07 7:08 ` Chao Yu
2020-12-05 7:40 ` [f2fs-dev] [PATCH 2/3] f2fs: inline: set FI_DATA_EXIST improperly Jack Qiu
2020-12-07 7:14 ` Chao Yu
2020-12-05 7:40 ` [f2fs-dev] [PATCH 3/3] f2fs: inline: fix wrong inline inode stat Jack Qiu
2020-12-07 7:18 ` 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=3f26303f-a942-77f2-fa1b-92302c08a022@huawei.com \
--to=yuchao0@huawei.com \
--cc=jack.qiu@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).