From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath-tools: add FUJITSU/ETERNUS 2000/4000/8000 to hwtable
Date: Sat, 22 Oct 2016 23:27:02 +0200 [thread overview]
Message-ID: <994ad78a-8531-28f4-e642-6b7233e321e8@gmail.com> (raw)
In-Reply-To: <20161008223049.00006901@gmx.de>
On 10/08/2016 10:30 PM, Sebastian Herbszt wrote:
> Now that you dropped the path selector as suggested back in July [1]
> why not merge this with the ETERNUS DX entry?
>
> [1] https://www.redhat.com/archives/dm-devel/2016-July/msg00595.html
If a lot of devices share the same configuration some flexibility is lost.
I do not have a single answer.
It's a tricky balance between to group devices and don't lose flexibility.
ETERNUS 2000/4000/8000 are very old and a different generation of devices,
the next year they are going to be declared "EOL" in Japan. In the rest of the
world it was at the beginning of 2015, IIRC.
prev parent reply other threads:[~2016-10-22 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 21:12 [PATCH] multipath-tools: add FUJITSU/ETERNUS 2000/4000/8000 to hwtable Xose Vazquez Perez
2016-10-08 20:30 ` Sebastian Herbszt
2016-10-22 21:27 ` Xose Vazquez Perez [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=994ad78a-8531-28f4-e642-6b7233e321e8@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=dm-devel@redhat.com \
--cc=herbszt@gmx.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