From: Jes Sorensen <jes@trained-monkey.org>
To: Lidong Zhong <lidong.zhong@suse.com>
Cc: linux-raid@vger.kernel.org, guoqing.jiang@cloud.ionos.com
Subject: Re: [PATCH] Detail: show correct bitmap info for cluster raid device
Date: Mon, 16 Mar 2020 17:50:35 -0400 [thread overview]
Message-ID: <46fbe3ac-f9e6-078d-a9cc-eb8457bf80b5@trained-monkey.org> (raw)
In-Reply-To: <20200316021649.4423-1-lidong.zhong@suse.com>
On 3/15/20 10:16 PM, Lidong Zhong wrote:
> Signed-off-by: Lidong Zhong <lidong.zhong@suse.com>
> ---
> Detail.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied!
Thanks,
Jes
next prev parent reply other threads:[~2020-03-16 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 2:16 [PATCH] Detail: show correct bitmap info for cluster raid device Lidong Zhong
2020-03-16 21:50 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-13 9:05 Lidong Zhong
2020-03-13 15:07 ` Guoqing Jiang
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=46fbe3ac-f9e6-078d-a9cc-eb8457bf80b5@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=lidong.zhong@suse.com \
--cc=linux-raid@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).