From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>,
"Schremmer, Steven" <Steve.Schremmer@netapp.com>
Cc: "George, Martin" <Martin.George@netapp.com>,
Hannes Reinecke <hare@suse.com>,
ng-eseries-upstream-maintainers
<ng-eseries-upstream-maintainers@netapp.com>,
DM-DEVEL ML <dm-devel@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: Re: [dm-devel] [PATCH 4/9] multipath-tools: add NetApp E-Series NVMe to hardware table
Date: Thu, 9 Jun 2022 18:56:00 +0200 [thread overview]
Message-ID: <7510d16e-b821-3030-16cf-ef39854109f5@gmail.com> (raw)
In-Reply-To: <8ab798a93edf33a550f0c78f113d8943d76916b6.camel@suse.com>
On 6/9/22 18:49, Martin Wilck wrote:
> IIUC NetApp's concern is not the generic entry, but the entries
> mentioning E-Series or it's OEM products in NVMe configuration
> explicitly. I also have some trouble understanding the concern, but
> NetApp is in charge of these entries, so I believe we should respect
> what they're saying.
>
> With the late patches I submitted, the generic NVMe defaults would work
> for the NetApp devices without those being explicitly mentioned. I hope
> this is ok for everyone. Only the no_path_retry setting would get lost,
> which is acceptable IMO because this is rather an admin setting than
> product-specific.
And now (IMO) it is worse, because NetApp NVMe arrays are under a generic config.
What do they hate? just ".product = "NetApp E-Series"" ???
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2022-06-09 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220514230148.139675-1-xose.vazquez@gmail.com>
2022-05-14 23:01 ` [dm-devel] [PATCH 1/9] multipath-tools: fix misspellings Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 2/9] multipath-tools: add HPE Alletra 9000 NVMe to hardware table Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 3/9] multipath-tools: delete redundant ONTAP NVMe comment Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 4/9] multipath-tools: add NetApp E-Series NVMe to hardware table Xose Vazquez Perez
2022-05-18 20:24 ` Schremmer, Steven
2022-05-19 9:30 ` Martin Wilck
2022-05-19 13:18 ` Schremmer, Steven
2022-05-19 14:46 ` Martin Wilck
2022-05-26 20:10 ` Schremmer, Steven
2022-05-31 8:43 ` Martin Wilck
2022-05-31 17:05 ` Benjamin Marzinski
2022-06-09 16:36 ` Xose Vazquez Perez
2022-06-09 16:49 ` Martin Wilck
2022-06-09 16:56 ` Xose Vazquez Perez [this message]
2022-06-09 17:00 ` Martin Wilck
2022-05-14 23:01 ` [dm-devel] [PATCH 5/9] multipath-tools: add Huawei OceanStor " Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 6/9] multipath-tools: add IBM FlashSystem(TMS RamSan) " Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 7/9] multipath-tools: add IBM FlashSystem(Storwize/SVC) " Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 8/9] multipath-tools: add Pure FlashArray " Xose Vazquez Perez
2022-05-14 23:01 ` [dm-devel] [PATCH 9/9] multipath-tools: add Dell EMC PowerStore " 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=7510d16e-b821-3030-16cf-ef39854109f5@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Martin.George@netapp.com \
--cc=Steve.Schremmer@netapp.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.com \
--cc=mwilck@suse.com \
--cc=ng-eseries-upstream-maintainers@netapp.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.