From: tang.junhui@zte.com.cn
To: mlyle@lyle.org
Cc: colyli@suse.de, linux-bcache@vger.kernel.org, tang.junhui@zte.com.cn
Subject: Re: [PATCH 2/2] bcache: fix high CPU occupancy during journal
Date: Thu, 1 Feb 2018 10:53:38 +0800 [thread overview]
Message-ID: <1517453618-16400-1-git-send-email-tang.junhui@zte.com.cn> (raw)
From: Tang Junhui <tang.junhui@zte.com.cn>
Hello Mike,
> LGTM on first read-- I'll read it again and test in test branch.
>
> Reviewed-by: Michael Lyle <mlyle@lyle.org>
>
Thanks very much for your review, if there is any issue in test,
please let me known.
Thanks.
Tang Junhui
next reply other threads:[~2018-02-01 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 2:53 tang.junhui [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-01 3:25 [PATCH 2/2] bcache: fix high CPU occupancy during journal tang.junhui
2018-01-26 8:24 tang.junhui
2018-02-01 2:31 ` Michael Lyle
2018-02-01 3:07 ` Michael Lyle
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=1517453618-16400-1-git-send-email-tang.junhui@zte.com.cn \
--to=tang.junhui@zte.com.cn \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=mlyle@lyle.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).