From: Hannes Reinecke <hare@suse.de>
To: dm-devel@redhat.com
Subject: Re: [PATCH 08/10] multipath-tools: remove USER_FRIENDLY_NAMES_OFF
Date: Mon, 20 Jun 2016 09:07:26 +0200 [thread overview]
Message-ID: <5767962E.7090800@suse.de> (raw)
In-Reply-To: <CABr-GneYSo9zHqsn45wsigTX+sMpu8SgEquBEU_4Qoka47XgZg@mail.gmail.com>
On 06/20/2016 08:58 AM, Christophe Varoqui wrote:
> I tend to agree with Xose this is unfair to set user_friendly_name in
> the hwtable entries.
> Does anybody have a vote against my merging this patch ?
>
> On Fri, Jun 17, 2016 at 4:52 PM, Xose Vazquez Perez
> <xose.vazquez@gmail.com <mailto:xose.vazquez@gmail.com>> wrote:
>
> This is up to sysadmins, and it is already off by default.
>
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com
> <mailto:christophe.varoqui@opensvc.com>>
> Cc: device-mapper development <dm-devel@redhat.com
> <mailto:dm-devel@redhat.com>>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com
> <mailto:xose.vazquez@gmail.com>>
> ---
> libmultipath/hwtable.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index 598b9b8..bef8d31 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -794,7 +794,6 @@ static struct hwentry default_hw[] = {
> .prio_name = PRIO_ONTAP,
> .prio_args = NULL,
> .retain_hwhandler = RETAIN_HWHANDLER_ON,
> - .user_friendly_names = USER_FRIENDLY_NAMES_OFF,
> .detect_prio = DETECT_PRIO_ON,
> },
> /*
> @@ -1133,7 +1132,6 @@ static struct hwentry default_hw[] = {
> .pgfailback = -FAILBACK_IMMEDIATE,
> .checker_name = TUR,
> .fast_io_fail = 10,
> - .user_friendly_names = USER_FRIENDLY_NAMES_OFF,
> .prio_name = DEFAULT_PRIO,
> .no_path_retry = 0,
No, indeed, that's fine.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
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)
next prev parent reply other threads:[~2016-06-20 7:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:52 [PATCH v2 01/10] multipath-tools: add VIOLIN/CONCERTO ARRAY to hardware table Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH v2 02/10] multipath-tools: add INFINIDAT devices " Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH v2 03/10] multipath-tools: add TEGILE " Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH 04/10] multipath-tools: remove current maintainer from orphan array families Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH v2 05/10] multipath-tools: unreachable controllers maintainers Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH 06/10] multipath-tools: new email address for Srinivas Ramani Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH 08/10] multipath-tools: remove USER_FRIENDLY_NAMES_OFF Xose Vazquez Perez
2016-06-20 6:58 ` Christophe Varoqui
2016-06-20 7:07 ` Hannes Reinecke [this message]
2016-06-20 10:42 ` Bryn M. Reeves
2016-06-17 14:52 ` [PATCH 09/10] multipath-tools: clean up comments at hwtable.c Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH 10/10] multipath-tools: group ONTAP family Xose Vazquez Perez
2016-06-17 14:52 ` [PATCH] multipath-tools: RDAC border Xose Vazquez Perez
[not found] ` <1466175169-16684-7-git-send-email-xose.vazquez@gmail.com>
2016-06-17 15:15 ` [PATCH 07/10] multipath-tools: dm-devel list is only for subscribers Xose Vazquez Perez
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=5767962E.7090800@suse.de \
--to=hare@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.