From: Chao Yu <chao@kernel.org>
To: Sahitya Tummala <stummala@codeaurora.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: show the CP_PAUSE reason in checkpoint traces
Date: Mon, 6 Jan 2020 22:04:45 +0800 [thread overview]
Message-ID: <83a00e37-bc83-b186-667f-089472d2b1df@kernel.org> (raw)
In-Reply-To: <1578021568-21552-1-git-send-email-stummala@codeaurora.org>
On 2020-1-3 11:19, Sahitya Tummala wrote:
> Remove the duplicate CP_UMOUNT enum and add the new CP_PAUSE
> enum to show the checkpoint reason in the trace prints.
>
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Sahitya Tummala <stummala@codeaurora.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: show the CP_PAUSE reason in checkpoint traces
Date: Mon, 6 Jan 2020 22:04:45 +0800 [thread overview]
Message-ID: <83a00e37-bc83-b186-667f-089472d2b1df@kernel.org> (raw)
In-Reply-To: <1578021568-21552-1-git-send-email-stummala@codeaurora.org>
On 2020-1-3 11:19, Sahitya Tummala wrote:
> Remove the duplicate CP_UMOUNT enum and add the new CP_PAUSE
> enum to show the checkpoint reason in the trace prints.
>
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
next prev parent reply other threads:[~2020-01-06 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 3:19 [f2fs-dev] [PATCH] f2fs: show the CP_PAUSE reason in checkpoint traces Sahitya Tummala
2020-01-03 3:19 ` Sahitya Tummala
2020-01-06 14:04 ` Chao Yu [this message]
2020-01-06 14:04 ` [f2fs-dev] " Chao Yu
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=83a00e37-bc83-b186-667f-089472d2b1df@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=yuchao0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.