From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org, osamarin68@gmail.com
Subject: Re: [MDADM PATCH 1/1] Add detail information when can not connect monitor
Date: Mon, 09 Jan 2017 07:50:35 -0500 [thread overview]
Message-ID: <wrfjbmvgfld0.fsf@redhat.com> (raw)
In-Reply-To: <1483844394-7647-1-git-send-email-xni@redhat.com> (Xiao Ni's message of "Sun, 8 Jan 2017 10:59:54 +0800")
Xiao Ni <xni@redhat.com> writes:
> If it can't connect monitor, now the error message is just
> Error waiting for xxx to be clean. Add detail error message
> in connect_monitor.
>
> Suggested-by: Oleg Samarin <osamarin68@gmail.com>
> Signed-off-by: Xiao Ni <xni@redhat.com>
> ---
> msg.c | 2 ++
> 1 file changed, 2 insertions(+)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2017-01-09 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 2:59 [MDADM PATCH 1/1] Add detail information when can not connect monitor Xiao Ni
2017-01-09 12:50 ` Jes Sorensen [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=wrfjbmvgfld0.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=osamarin68@gmail.com \
--cc=xni@redhat.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 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).