From: Jes Sorensen <jes.sorensen@gmail.com>
To: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Don't use UnSet with consistency_policy
Date: Mon, 24 Apr 2017 17:11:25 -0400 [thread overview]
Message-ID: <64c55eb2-37a7-4f3c-e0cb-4b3e6e77e9a0@gmail.com> (raw)
In-Reply-To: <20170424140326.2707-1-artur.paszkiewicz@intel.com>
On 04/24/2017 10:03 AM, Artur Paszkiewicz wrote:
> Use CONSISTENCY_POLICY_UNKNOWN instead. Simplify some checks because
> since 5e8e35fb7e17 ("maps: Use keyvalue for null terminator to indicate
> 'unset' value") map_name() can return this default directly.
>
> Suggested-by: Jes Sorensen <Jes.Sorensen@gmail.com>
> Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
> ---
> maps.c | 2 +-
> mdadm.c | 12 ++++++------
> super-intel.c | 4 +---
> sysfs.c | 10 ++++------
> 4 files changed, 12 insertions(+), 16 deletions(-)
Applied!
Thanks,
Jes
prev parent reply other threads:[~2017-04-24 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 14:03 [PATCH] Don't use UnSet with consistency_policy Artur Paszkiewicz
2017-04-24 21:11 ` 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=64c55eb2-37a7-4f3c-e0cb-4b3e6e77e9a0@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=artur.paszkiewicz@intel.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).