From: Patrick Mansfield <patmans@us.ibm.com>
To: Ingo Flaschberger <if@xip.at>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Matthew Wilcox <matthew@wil.cx>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch
Date: Thu, 30 Mar 2006 08:13:58 -0800 [thread overview]
Message-ID: <20060330161358.GA3237@us.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0603301719200.6412@filebunker.xip.at>
On Thu, Mar 30, 2006 at 05:54:48PM +0200, Ingo Flaschberger wrote:
> + {"COMPAQ", "ARRAY CONTROLLER", "2.60", BLIST_SPARSELUN | BLIST_LARGELUN |
> + BLIST_MAX_512K | BLIST_REPORTLUN}, /* Compaq RA4x00 */
> + {"COMPAQ", "LOGICAL VOLUME", "2.60", BLIST_MAX_512K}, /* Compaq RA4x00 */
> {"COMPAQ", "LOGICAL VOLUME", NULL, BLIST_FORCELUN},
Related to Matthew's question ...
The revision field is not used, so you should combine the above into one
entry, else the first one will always be used.
-- Patrick Mansfield
next prev parent reply other threads:[~2006-03-30 16:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 23:55 Compaq Fiber Channel Array RM4000 / Scsi middle ware driver Ingo Flaschberger
2006-02-28 0:23 ` Ingo Flaschberger
2006-02-28 0:32 ` Ingo Flaschberger
2006-02-28 0:40 ` Matthew Wilcox
2006-03-22 18:17 ` Ingo Flaschberger
2006-03-22 18:41 ` Martin K. Petersen
2006-03-22 19:58 ` Ingo Flaschberger
2006-03-22 20:02 ` Matthew Wilcox
2006-03-22 20:13 ` Ingo Flaschberger
2006-03-28 19:43 ` Compaq Fiber Channel Array RM4000 / SCSI Problems / Need HELP! Ingo Flaschberger
2006-03-29 6:07 ` Martin K. Petersen
2006-03-29 11:17 ` Ingo Flaschberger
2006-03-29 13:10 ` Compaq Fiber Channel Array RM4000 / Kernel implementation Ingo Flaschberger
2006-03-29 13:19 ` typo in scsi_devinfo.h Ingo Flaschberger
2006-03-29 13:43 ` Matthew Wilcox
2006-03-29 15:07 ` Compaq Fiber Channel Array RM4000 / Kernel implementation Christoph Hellwig
2006-03-29 16:47 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch Ingo Flaschberger
2006-03-29 17:29 ` James Bottomley
2006-03-29 17:53 ` Ingo Flaschberger
2006-03-29 18:22 ` James Bottomley
2006-03-29 18:35 ` Ingo Flaschberger
2006-03-29 18:43 ` James Bottomley
2006-03-29 18:54 ` Ingo Flaschberger
2006-03-29 19:03 ` James Bottomley
2006-03-29 20:23 ` Ingo Flaschberger
2006-03-29 21:11 ` James Bottomley
2006-03-30 10:53 ` Ingo Flaschberger
2006-03-30 12:58 ` Matthew Wilcox
2006-03-30 14:20 ` Ingo Flaschberger
2006-03-30 14:46 ` James Bottomley
2006-03-30 15:04 ` Ingo Flaschberger
2006-03-30 15:09 ` James Bottomley
2006-03-30 15:54 ` Ingo Flaschberger
2006-03-30 16:13 ` Patrick Mansfield [this message]
2006-03-30 16:25 ` Ingo Flaschberger
2006-03-30 16:24 ` Matthew Wilcox
2006-03-30 16:35 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch VER6 Ingo Flaschberger
2006-03-31 17:36 ` Ingo Flaschberger
2006-03-31 19:45 ` James Bottomley
2006-03-31 21:13 ` Ingo Flaschberger
2006-03-31 21:21 ` James Bottomley
2006-03-31 21:24 ` Ingo Flaschberger
2006-04-01 1:16 ` Ingo Flaschberger
2006-04-01 2:07 ` James Bottomley
2006-04-01 16:46 ` Ingo Flaschberger
2006-04-06 11:21 ` Compaq Fiber Channel Array RM4000 / 2.6.16 kernel patch VER7 Ingo Flaschberger
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=20060330161358.GA3237@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=if@xip.at \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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).