From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs-tools: add periodic check in kernel version check
Date: Sat, 17 Jul 2021 19:04:14 +0800 [thread overview]
Message-ID: <57f7ac57-03f5-e9cf-6850-d5e5c2948242@kernel.org> (raw)
In-Reply-To: <20210716215703.1560325-1-daeho43@gmail.com>
On 2021/7/17 5:57, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> In previous, we did a full scan right after kernel version is changed
> and it triggered many unnecessary full scan whenever a newly built
> kernel is downloaded. Plus, we are lack of a periodic health check of
> on-disk filesystem images. So, I added a monthly periodic check after
> a new vesion is updated.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2021-07-17 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 21:57 [PATCH] f2fs-tools: add periodic check in kernel version check Daeho Jeong
2021-07-17 11:04 ` 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=57f7ac57-03f5-e9cf-6850-d5e5c2948242@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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).