From: jes.sorensen@gmail.com
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/4] mdadm:checking level once mode has been set
Date: Fri, 17 Mar 2017 15:30:08 -0400 [thread overview]
Message-ID: <wrfjy3w3k8fz.fsf@gmail.com> (raw)
In-Reply-To: <20170308074831.24683-1-zlliu@suse.com> (Zhilong Liu's message of "Wed, 8 Mar 2017 15:48:31 +0800")
Zhilong Liu <zlliu@suse.com> writes:
> mdadm: it would be better to check --level ealier,
> because it would fall to different prompt if user
> forgets to specify the --level. such as:
> ./mdadm -CR /dev/md0 -b internal -n2 -x1 /dev/loop[0-2]
>
> Signed-off-by: Zhilong Liu <zlliu@suse.com>
This patchset is completely messed up - 0/4 contains actual code instead
of being a cover letter. 5/5 is a reply to 1/4 and you posted a v1 of
something which I assume needs to be the v2 given the v1 is the original
posting.
Would you mind sending out a clean set of these patches?
Thanks,
Jes
prev parent reply other threads:[~2017-03-17 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 7:48 [PATCH 0/4] mdadm:checking level once mode has been set Zhilong Liu
2017-03-08 7:50 ` [PATCH 1/4] mdadm:bitmap cannot be set twice Zhilong Liu
2017-03-08 8:07 ` [PATCH 5/5] mdadm:checking level once mode has been set Zhilong Liu
2017-03-08 7:51 ` [PATCH 2/4] mdadm:external bitmap only supports ext filesystem Zhilong Liu
2017-03-12 14:48 ` Liu Zhilong
2017-03-13 8:16 ` zhilong
2017-03-08 7:52 ` [PATCH 3/4] mdadm:triggers core dump when stat2devnm return NULL Zhilong Liu
2017-03-12 23:00 ` NeilBrown
2017-03-13 5:34 ` zhilong
2017-03-13 7:01 ` [PATCH 3/4 v1] " Zhilong Liu
2017-03-12 22:54 ` [PATCH 0/4] mdadm:checking level once mode has been set NeilBrown
2017-03-13 3:22 ` zhilong
2017-03-13 3:48 ` NeilBrown
2017-03-13 5:16 ` zhilong
2017-03-17 19:30 ` 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=wrfjy3w3k8fz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.