From: Babu Moger <babu.moger@oracle.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>,
SCSI ML <linux-scsi@vger.kernel.org>,
device-mapper development <dm-devel@redhat.com>
Cc: Sean Stewart <Sean.Stewart@netapp.com>,
Hannes Reinecke <hare@suse.de>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: update rdac devices at scsi_dh_rdac
Date: Tue, 18 Oct 2016 14:47:08 -0500 [thread overview]
Message-ID: <39e5713e-5329-80a2-d2c5-d193f974e270@oracle.com> (raw)
In-Reply-To: <eb9d6973-2e0b-843b-4547-94b64dcd05fc@gmail.com>
At this point, I am not the right person to ack this change. However,
adding new vendor id's is mostly not an issue.
But, removing could be a problem. Sean has to confirm this.
On 10/18/2016 10:11 AM, Xose Vazquez Perez wrote:
> On 10/07/2016 06:55 PM, Xose Vazquez Perez wrote:
>
> This patch is pending, ACK is needed!
> The part of multipath-tools was done time ago.
>
> CC: Babu Moger, just in case.
>
>> Remove IBM/1745 ghost array.
>> There is no references nowhere, also removed from multipath-tools
>> Confirmed by the original manufacturer(NetApp), and Google shows no results.
>>
>> Replace too wide "TP9" regex with full names.
>> TP9100 is included, at it is not a RDAC array.
>> This reverts partially the commit 352047
>>
>> Add IBM 3542 and 3552, they are FAStT200 and FAStT500
>>
>> Cc: Sean Stewart <Sean.Stewart@netapp.com>
>> Cc: Hannes Reinecke <hare@suse.de>
>> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
>> Cc: James E.J. Bottomley <jejb@linux.vnet.ibm.com>
>> Cc: Martin K. Petersen <martin.petersen@oracle.com>
>> Cc: SCSI ML <linux-scsi@vger.kernel.org>
>> Cc: device-mapper development <dm-devel@redhat.com>
>> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
>> ---
>> drivers/scsi/scsi_dh.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/scsi/scsi_dh.c b/drivers/scsi/scsi_dh.c
>> index b8d3b97..a64b5ce 100644
>> --- a/drivers/scsi/scsi_dh.c
>> +++ b/drivers/scsi/scsi_dh.c
>> @@ -49,14 +49,18 @@ static const struct scsi_dh_blist scsi_dh_blist[] = {
>> {"IBM", "1724", "rdac", },
>> {"IBM", "1726", "rdac", },
>> {"IBM", "1742", "rdac", },
>> - {"IBM", "1745", "rdac", },
>> {"IBM", "1746", "rdac", },
>> {"IBM", "1813", "rdac", },
>> {"IBM", "1814", "rdac", },
>> {"IBM", "1815", "rdac", },
>> {"IBM", "1818", "rdac", },
>> {"IBM", "3526", "rdac", },
>> - {"SGI", "TP9", "rdac", },
>> + {"IBM", "3542", "rdac", },
>> + {"IBM", "3552", "rdac", },
>> + {"SGI", "TP9300", "rdac", },
>> + {"SGI", "TP9400", "rdac", },
>> + {"SGI", "TP9500", "rdac", },
>> + {"SGI", "TP9700", "rdac", },
>> {"SGI", "IS", "rdac", },
>> {"STK", "OPENstorage D280", "rdac", },
>> {"STK", "FLEXLINE 380", "rdac", },
>>
next prev parent reply other threads:[~2016-10-18 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 16:55 [PATCH] scsi: update rdac devices at scsi_dh_rdac Xose Vazquez Perez
2016-10-18 15:11 ` Xose Vazquez Perez
2016-10-18 19:47 ` Babu Moger [this message]
2016-10-22 21:41 ` 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=39e5713e-5329-80a2-d2c5-d193f974e270@oracle.com \
--to=babu.moger@oracle.com \
--cc=Sean.Stewart@netapp.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=xose.vazquez@gmail.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;
as well as URLs for NNTP newsgroup(s).