From: Neil Brown <neilb@suse.de>
To: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@intel.com>
Cc: linux-raid@vger.kernel.org, wojciech.neubauer@intel.com,
dan.j.williams@intel.com, ed.ciechanowski@intel.com
Subject: Re: [PATCH 0/5] Autorebuild, spare/spare-same-slot fixes
Date: Sun, 26 Dec 2010 22:40:19 +1100 [thread overview]
Message-ID: <20101226224019.33daa533@notabene.brown> (raw)
In-Reply-To: <20101223155614.5562.4773.stgit@gklab-170-211.igk.intel.com>
On Thu, 23 Dec 2010 17:02:00 +0100 Przemyslaw Czarnowski
<przemyslaw.hawrylewicz.czarnowski@intel.com> wrote:
> The following series changes (improves) behaviors implemented so far in
> Incremental for bare disks.
> It enables some features for containers working so far only for native
> metadata (size check and degradation) and fixes domain checking for
> "same slot" action.
>
> ---
>
> Przemyslaw Czarnowski (5):
> external: get number of failed disks for container
> Added test for array degradation for spare-same-slot
> Skip domain check for spare-same-slot
> Validate size of potential spare disk for external metadata (with containers)
> Consider target only for spare-same-domain
>
Thanks. All of these applied, with one changes as I described separately.
NeilBrown
prev parent reply other threads:[~2010-12-26 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 16:02 [PATCH 0/5] Autorebuild, spare/spare-same-slot fixes Przemyslaw Czarnowski
2010-12-23 16:02 ` [PATCH 1/5] external: get number of failed disks for container Przemyslaw Czarnowski
2010-12-26 11:33 ` Neil Brown
2010-12-23 16:03 ` [PATCH 2/5] Added test for array degradation for spare-same-slot Przemyslaw Czarnowski
2010-12-23 16:03 ` [PATCH 3/5] Skip domain check " Przemyslaw Czarnowski
2010-12-23 16:04 ` [PATCH 4/5] Validate size of potential spare disk for external metadata (with containers) Przemyslaw Czarnowski
2010-12-23 16:04 ` [PATCH 5/5] Consider target only for spare-same-domain Przemyslaw Czarnowski
2010-12-26 11:40 ` Neil Brown [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=20101226224019.33daa533@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.com \
--cc=wojciech.neubauer@intel.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).