From: "Wilcox, Stephen P, CITPC" <spwilcox@att.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi mailing list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] DEC hsg80 needs BLIST_REPORTLUN2
Date: Tue, 9 Aug 2005 13:29:04 -0500 [thread overview]
Message-ID: <1123612144.30193.31.camel@aptis101.cqtel.com> (raw)
In-Reply-To: <1123609899.5170.32.camel@mulgrave>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Crap. I was afraid that my mailer might mangle this... I created the
patch with "diff -up" based on the info in "SubmittingPatches" in the
kernel source tree, but I must admit that I manually edited the patch so
that It would apply to RedHat's .src.rpms using their canned spec files.
The working (at least using RedHat's method) patch is attached this time
rather than pasted in. If that one still fails to work, the single
change is all that's really needed.
-steve
On Tue, 2005-08-09 at 12:51 -0500, James Bottomley wrote:
> On Tue, 2005-08-09 at 13:26 -0400, Steve Wilcox wrote:
> > In order to properly report LUN's > 7, the DEC HSG80 definition in
> > scsi_devinfo.c needs to include BLIST_REPORTLUN2 rather than
> > BLIST_SPARSELUN. I've tested this change with several HSG firmware
> > revisions and with both Emulex and Qlogic HBA's.
>
> Well, your patch won't apply. Apart from the breaking by the mailer,
> you have a curiosity in the last three lines (the DELL arrays) which are
> definitely missing tabs and spaces over what we have in the kernel
> (There are three spaces between "PV660F" and "PSEUDO" and there's a tab
> not a space before the comment). How did you generate this diff?
>
> Anyway, I can apply the single change manually.
>
> James
>
>
[-- Attachment #2: Replaced Blocked File.txt --]
[-- Type: text/plain, Size: 511 bytes --]
******** McAfee GroupShield Exchange **********
******** Alert generated at: Tuesday, August 09, 2005 01:29:05 PM Central Daylight Time
**********************************************************************
The file scsi-blacklist.patch has been replaced, as it is a file type that is known for spreading viruses. For assistance, please contact your local Desktop Support Personnel or refer to the following website for direction. http://antivirus.security.att.com/Default.htm
next prev parent reply other threads:[~2005-08-09 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 17:26 [PATCH] DEC hsg80 needs BLIST_REPORTLUN2 Steve Wilcox
2005-08-09 17:51 ` James Bottomley
2005-08-09 18:29 ` Wilcox, Stephen P, CITPC [this message]
2005-08-09 18:36 ` James Bottomley
2005-08-09 18:45 ` Steve Wilcox
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=1123612144.30193.31.camel@aptis101.cqtel.com \
--to=spwilcox@att.com \
--cc=James.Bottomley@SteelEye.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox