From: Joel Buckley <joel.buckley@sun.com>
To: axboe@suse.de, linux-scsi@vger.kernel.org, joel.buckley@sun.com
Subject: 2.4.20 & 2.5.63 scsi_scan.c for Sun StorEdge[tm] array SparseLUN support
Date: Mon, 24 Feb 2003 16:07:59 -0700 [thread overview]
Message-ID: <3E5AA5CF.6090501@sun.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
Jens, et.al.,
Hello, I work on the Sun StorEdge[tm] arrays for Sun Microsystems, Inc.
As part of my testing of Linux, the attached changes are needed to enable
Sparse LUN support for Sun StorEdge[tm] arrays.
Please apply to Both the 2.4.20 and 2.5.63 kernel releases.
If there are any questions, please contact me directly.
Thank you,
Joel.
--
Joel.Buckley@Sun.COM
Sun Microsystems, Inc.
303-272-5556 x75556
[-- Attachment #2: linux-2.4.20-scsi_scan.c.diffs --]
[-- Type: text/plain, Size: 432 bytes --]
--- linux-2.4.20/drivers/scsi/scsi_scan.c Thu Nov 28 16:53:14 2002
+++ linux-2.4.20/drivers/scsi/scsi_scan.c Mon Feb 24 15:53:48 2003
@@ -182,6 +182,8 @@
{"HITACHI", "DF500", "*", BLIST_SPARSELUN},
{"HITACHI", "DF600", "*", BLIST_SPARSELUN},
{"IBM", "ProFibre 4000R", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
+ {"SUN", "T300", "*", BLIST_SPARSELUN},
+ {"SUN", "T4", "*", BLIST_SPARSELUN},
/*
* Must be at end of list...
[-- Attachment #3: linux-2.5.63-scsi_scan.c.diffs --]
[-- Type: text/plain, Size: 427 bytes --]
--- linux-2.5.63/drivers/scsi/scsi_scan.c Mon Feb 24 12:05:39 2003
+++ linux-2.5.63/drivers/scsi/scsi_scan.c Mon Feb 24 16:00:46 2003
@@ -189,6 +189,8 @@
{"HITACHI", "DF500", "*", BLIST_SPARSELUN},
{"HITACHI", "DF600", "*", BLIST_SPARSELUN},
{"IBM", "ProFibre 4000R", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
+ {"SUN", "T300", "*", BLIST_SPARSELUN},
+ {"SUN", "T4", "*", BLIST_SPARSELUN},
{ NULL, NULL, NULL, 0 },
};
reply other threads:[~2003-02-24 23:07 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=3E5AA5CF.6090501@sun.com \
--to=joel.buckley@sun.com \
--cc=axboe@suse.de \
--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.