From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Guoqing Jiang <gqjiang@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] super1: add more checks for NodeNumUpdate option
Date: Thu, 12 May 2016 15:45:24 -0400 [thread overview]
Message-ID: <wrfjzirv83hn.fsf@redhat.com> (raw)
In-Reply-To: <1462959096-11272-1-git-send-email-gqjiang@suse.com> (Guoqing Jiang's message of "Wed, 11 May 2016 17:31:36 +0800")
Guoqing Jiang <gqjiang@suse.com> writes:
> There are some cases which didn't need to check the space
> is enough or not for NodeNumUpdate option.
>
> 1. for array which does not have clustered bitmap.
> 2. "--nodes" parameter is 0 (eg, add a disk to clustered raid).
> 3. if "--nodes" parameter is set to a smaller num than
> current bms->nodes.
>
> Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
> ---
> super1.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2016-05-12 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:31 [PATCH] super1: add more checks for NodeNumUpdate option Guoqing Jiang
2016-05-12 19:45 ` 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=wrfjzirv83hn.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=gqjiang@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).