From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
To: "heming.zhao@suse.com" <heming.zhao@suse.com>,
linux-raid@vger.kernel.org
Cc: neilb@suse.com
Subject: Re: cluster-md mddev->in_sync & mddev->safemode_delay may have bug
Date: Wed, 15 Jul 2020 21:12:57 +0200 [thread overview]
Message-ID: <c5b3d5c0-bfc5-37b7-b00e-f6f10b5edc3f@cloud.ionos.com> (raw)
In-Reply-To: <57e70970-814b-3a55-35cc-b1415a301895@suse.com>
On 7/15/20 8:40 PM, heming.zhao@suse.com wrote:
> Hello Guoqing,
>
> Thank you for your kindly reply and review comments. I will resend
> that patch later.
>
> Do you know who take care of cluster-md field in this mail list?
> I want he/she to shed a little light on me.
I think no one is dedicated to it, and Song covers all the md stuffs. I
can comment it
once I am not busy.
Thanks,
Guoqing
next prev parent reply other threads:[~2020-07-15 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 3:48 cluster-md mddev->in_sync & mddev->safemode_delay may have bug heming.zhao
2020-07-15 18:17 ` Guoqing Jiang
2020-07-15 18:40 ` heming.zhao
2020-07-15 19:12 ` Guoqing Jiang [this message]
2020-07-16 0:54 ` NeilBrown
2020-07-16 5:52 ` heming.zhao
2020-07-16 6:10 ` Song Liu
2020-07-16 6:22 ` heming.zhao
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=c5b3d5c0-bfc5-37b7-b00e-f6f10b5edc3f@cloud.ionos.com \
--to=guoqing.jiang@cloud.ionos.com \
--cc=heming.zhao@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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