From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 2/2] Merge Dell MD3XXX hardware table entries
Date: Tue, 10 May 2016 18:31:19 +0200 [thread overview]
Message-ID: <cc3da002-69be-5b0e-f140-5b29f67fde7a@gmail.com> (raw)
Hannes Reinecke wrote(2015-03-30 6:23:23):
> Remove duplicate entries and merge MD36xxi/MD36xxf into a single
> one.
>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
> libmultipath/hwtable.c | 53 ++++----------------------------------------------
> 1 file changed, 4 insertions(+), 49 deletions(-)
>
> diff --git a/libmultipath/hwtable.c b/libmultipath/hwtable.c
> index fa4b20f..f83f3e7 100644
> --- a/libmultipath/hwtable.c
> +++ b/libmultipath/hwtable.c
> @@ -728,7 +728,7 @@ static struct hwentry default_hw[] = {
> .prio_args = NULL,
> },
> {
> - /* DELL MD3000 */
> + /* DELL MD3000/MD3000i */
> .vendor = "DELL",
> .product = "MD3000",
> .bl_product = "Universal Xport",
> @@ -743,22 +743,7 @@ static struct hwentry default_hw[] = {
> .prio_args = NULL,
> },
> {
> - /* DELL MD3000i */
> - .vendor = "DELL",
> - .product = "MD3000i",
> - .bl_product = "Universal Xport",
> - .features = "2 pg_init_retries 50",
> - .hwhandler = "1 rdac",
> - .pgpolicy = GROUP_BY_PRIO,
> - .pgfailback = -FAILBACK_IMMEDIATE,
> - .rr_weight = RR_WEIGHT_NONE,
> - .no_path_retry = 15,
> - .checker_name = RDAC,
> - .prio_name = PRIO_RDAC,
> - .prio_args = NULL,
> - },
> - {
> - /* DELL MD32xx */
> + /* DELL MD32xx/MD32xxi */
> .vendor = "DELL",
> .product = "MD32xx",
> .bl_product = "Universal Xport",
> @@ -773,39 +758,9 @@ static struct hwentry default_hw[] = {
> .prio_args = NULL,
> },
> {
> - /* DELL MD32xxi */
> - .vendor = "DELL",
> - .product = "MD32xxi",
> - .bl_product = "Universal Xport",
> - .features = "2 pg_init_retries 50",
> - .hwhandler = "1 rdac",
> - .pgpolicy = GROUP_BY_PRIO,
> - .pgfailback = -FAILBACK_IMMEDIATE,
> - .rr_weight = RR_WEIGHT_NONE,
> - .no_path_retry = 15,
> - .checker_name = RDAC,
> - .prio_name = PRIO_RDAC,
> - .prio_args = NULL,
> - },
> - {
> - /* DELL MD36xxi */
> - .vendor = "DELL",
> - .product = "MD36xxi",
> - .bl_product = "Universal Xport",
> - .features = "2 pg_init_retries 50",
> - .hwhandler = "1 rdac",
> - .pgpolicy = GROUP_BY_PRIO,
> - .pgfailback = -FAILBACK_IMMEDIATE,
> - .rr_weight = RR_WEIGHT_NONE,
> - .no_path_retry = 15,
> - .checker_name = RDAC,
> - .prio_name = PRIO_RDAC,
> - .prio_args = NULL,
> - },
> - {
> - /* DELL MD36xxf */
> + /* DELL MD36xxi/MD36xxf */
> .vendor = "DELL",
> - .product = "MD36xxf",
> + .product = "MD36xx(i|f)",
> .bl_product = "Universal Xport",
> .features = "2 pg_init_retries 50",
> .hwhandler = "1 rdac",
> --
> 1.8.4.5
This patch is missing in upstream git.
next reply other threads:[~2016-05-10 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:31 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-19 17:33 [PATCH 2/2] Merge Dell MD3XXX hardware table entries Xose Vazquez Perez
2015-03-30 6:23 [PATCH 1/2] Remove duplicate hwtable entry for XtremIO Hannes Reinecke
2015-03-30 6:23 ` [PATCH 2/2] Merge Dell MD3XXX hardware table entries Hannes Reinecke
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=cc3da002-69be-5b0e-f140-5b29f67fde7a@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
/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