From: Jeremy Higdon <jeremy@sgi.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH] 2.6.3 - remove some SGI devices from scsi_static_device_list
Date: Tue, 24 Feb 2004 20:09:07 -0800 [thread overview]
Message-ID: <20040225040907.GA556235@sgi.com> (raw)
Some SGI RAID devices identify as being SCSI-3, so they don't need
to be in the scsi_static_device_list any more. I've tested to make
sure that all luns still show up in a sparse, large config.
So I'm proposing removing them. Thanks to hch for the suggestion.
jeremy
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1588.3.1 -> 1.1588.3.2
# drivers/scsi/scsi_devinfo.c 1.7 -> 1.8
#
# --------------------------------------------
# 04/02/23 jeremy@tomahawk.engr.sgi.com 1.1588.3.2
# Remove SGI TP9300, TP9400, and TP9500. They advertise as SCSI-3, so they
# don't need to be on the device list.
# --------------------------------------------
#
diff -Nru a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
--- a/drivers/scsi/scsi_devinfo.c Tue Feb 24 20:03:48 2004
+++ b/drivers/scsi/scsi_devinfo.c Tue Feb 24 20:03:48 2004
@@ -178,9 +178,6 @@
{"SGI", "RAID3", "*", BLIST_SPARSELUN},
{"SGI", "RAID5", "*", BLIST_SPARSELUN},
{"SGI", "TP9100", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
- {"SGI", "TP9300", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
- {"SGI", "TP9400", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
- {"SGI", "TP9500", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
{"MYLEX", "DACARMRB", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
{"XYRATEX", "RS", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
{ NULL, NULL, NULL, 0 },
reply other threads:[~2004-02-25 4:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040225040907.GA556235@sgi.com \
--to=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
/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.