From: jes.sorensen@gmail.com
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH v1] mdadm/Build:check the level parameter when build new array
Date: Tue, 28 Mar 2017 14:27:01 -0400 [thread overview]
Message-ID: <wrfjinmtfea2.fsf@gmail.com> (raw)
In-Reply-To: <20170328135227.6081-1-zlliu@suse.com> (Zhilong Liu's message of "Tue, 28 Mar 2017 21:52:27 +0800")
Zhilong Liu <zlliu@suse.com> writes:
> check if user forgets to specify the --level
> when build a new array. such as:
> ./mdadm -B /dev/md0 -n2 /dev/loop[0-1]
>
> Signed-off-by: Zhilong Liu <zlliu@suse.com>
> ---
> Build.c | 4 ++++
> 1 file changed, 4 insertions(+)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2017-03-28 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 5:17 [PATCH] mdadm:checking --level once mode has been set Zhilong Liu
2017-03-27 21:59 ` jes.sorensen
2017-03-28 13:52 ` [PATCH v1] mdadm/Build:check the level parameter when build new array Zhilong Liu
2017-03-28 18:27 ` 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=wrfjinmtfea2.fsf@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=zlliu@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;
as well as URLs for NNTP newsgroup(s).