From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't clear CP_QUOTA_NEED_FSCK_FLAG
Date: Thu, 28 Feb 2019 09:08:27 +0800 [thread overview]
Message-ID: <f5b5832f-293c-a794-f55f-0a5e46031d07@huawei.com> (raw)
In-Reply-To: <20190226175725.GB59048@jaegeuk-macbookpro.roam.corp.google.com>
On 2019/2/27 1:57, Jaegeuk Kim wrote:
> /*
> * TODO: we count on fsck.f2fs to clear this flag until we figure out
> * missing cases which clear it incorrectly.
> */
>
> I added like this.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
>
> Thanks,
next prev parent reply other threads:[~2019-02-28 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 2:33 [PATCH] f2fs: don't clear CP_QUOTA_NEED_FSCK_FLAG Jaegeuk Kim
2019-02-13 3:42 ` [f2fs-dev] " Chao Yu
2019-02-16 4:55 ` Jaegeuk Kim
2019-02-18 9:10 ` [f2fs-dev] " Chao Yu
2019-02-20 7:08 ` Jaegeuk Kim
2019-02-20 7:25 ` Chao Yu
2019-02-20 7:31 ` Chao Yu
2019-02-22 2:40 ` Jaegeuk Kim
2019-02-22 3:27 ` Chao Yu
2019-02-26 17:57 ` Jaegeuk Kim
2019-02-28 1:08 ` Chao Yu [this message]
2019-05-10 9:45 ` Chao Yu
2019-05-20 23:24 ` 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=f5b5832f-293c-a794-f55f-0a5e46031d07@huawei.com \
--to=yuchao0@huawei.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).