From: Jes Sorensen <jes.sorensen@gmail.com>
To: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Detail: differentiate between container and inactive arrays
Date: Wed, 23 Aug 2017 13:43:07 -0400 [thread overview]
Message-ID: <13b894c3-a7b7-5d7e-46cc-a653eb04282c@gmail.com> (raw)
In-Reply-To: <1503050423-20984-1-git-send-email-mariusz.tkaczyk@intel.com>
On 08/18/2017 06:00 AM, Mariusz Tkaczyk wrote:
> Containers used to be handled as active arrays because GET_ARRAY_INFO
> ioctl returns valid structure for them. As containers appear as inactive
> in sysfs, the output for detail command has changed.
>
> Stop relying on inactive state for containers. Make the output look the
> same as in mdadm 4.0.
>
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com>
Applied!
Thanks,
Jes
prev parent reply other threads:[~2017-08-23 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 10:00 [PATCH] Detail: differentiate between container and inactive arrays Mariusz Tkaczyk
2017-08-23 17:43 ` 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=13b894c3-a7b7-5d7e-46cc-a653eb04282c@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@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).