Linux Device Mapper development
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Benjamin Marzinski <bmarzins@redhat.com>,
	device-mapper development <dm-devel@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH 0/3][RESEND] resending find_multipaths patches
Date: Mon, 16 Mar 2015 08:54:43 +0100	[thread overview]
Message-ID: <55068C43.8060401@suse.de> (raw)
In-Reply-To: <1426271247-21345-1-git-send-email-bmarzins@redhat.com>

On 03/13/2015 07:27 PM, Benjamin Marzinski wrote:
> I'm resending my find_multipaths patch, based on the conversation I had
> here. If nothing else, I'd at least like a discussion about why these
> shouldn't go in.
> 
> http://www.redhat.com/archives/dm-devel/2014-July/msg00029.html
> 
> Just to clarify. find_multipaths is a configurable option that when set to
> 'yes' will make multipath only run on devices have more than one path.  This
> means that users can mostly leave the blacklist alone, and they will only get
> the multipath devices that they want. The only time the blacklist is necessary
> is when users actually have multiple paths to a device, but still don't want
> multipath set up on it.  It's been around since RHEL6, and it is turned on
> in the default multipath.conf file in RHEL7. The internal default is "off".
> 
> Hannes, do you still object to these?
> 
> Benjamin Marzinski (3):
>   add find_multipaths option
>   libmultipath: only add uninitialized paths in check_path
>   Add find_multipaths to multipath.conf man page
> 
>  libmultipath/config.c      |  1 +
>  libmultipath/config.h      |  1 +
>  libmultipath/configure.c   | 11 +++++++++++
>  libmultipath/defaults.h    |  1 +
>  libmultipath/dict.c        |  4 ++++
>  libmultipath/discovery.c   |  2 ++
>  libmultipath/structs.h     |  1 +
>  libmultipath/wwids.c       | 26 ++++++++++++++++++++++++++
>  libmultipath/wwids.h       |  1 +
>  multipath/main.c           | 27 +++++++++++++++++++++++++--
>  multipath/multipath.conf.5 | 22 ++++++++++++++++++++++
>  multipathd/main.c          |  9 +++++++++
>  12 files changed, 104 insertions(+), 2 deletions(-)
> 
Patchset is fine now. We've discussed all the issues already, and
from my side this should be okay.

Acked-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

      parent reply	other threads:[~2015-03-16  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 18:27 [PATCH 0/3][RESEND] resending find_multipaths patches Benjamin Marzinski
2015-03-13 18:27 ` [PATCH 1/3] add find_multipaths option Benjamin Marzinski
2015-03-13 18:27 ` [PATCH 2/3] libmultipath: only add uninitialized paths in check_path Benjamin Marzinski
2015-03-13 18:27 ` [PATCH 3/3] Add find_multipaths to multipath.conf man page Benjamin Marzinski
2015-03-14  9:57 ` [PATCH 0/3][RESEND] resending find_multipaths patches Christophe Varoqui
2015-03-16  7:54 ` Hannes Reinecke [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=55068C43.8060401@suse.de \
    --to=hare@suse.de \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@gmail.com \
    --cc=dm-devel@redhat.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