From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Moore, Eric Dean" <Eric.Moore@lsil.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SPI transport class and generic Domain Validation for fusion
Date: Tue, 09 Aug 2005 09:47:10 -0500 [thread overview]
Message-ID: <1123598830.5170.19.camel@mulgrave> (raw)
In-Reply-To: <20050809091353.GA11397@infradead.org>
On Tue, 2005-08-09 at 10:13 +0100, Christoph Hellwig wrote:
> - there's a stale printk("HERE2\n"); in mptscsih_writeSDP1.
Yes, sorry, I'll remove it
> - the #undef MPTSCSIH_ENABLE_DOMAIN_VALIDATION is probably not needed
There's actually an awful lot of other cruft besides this that can come
out of the driver (inquiry snooping leaps to mind).
> - the hd == NULL check in mptspi_target_alloc isn't needed
Yes, OK.
> - should the driver print a warning about too old firmware when we can't
> access page 0?
I'll defer to LSI on this one. We can't attach the transport classes in
this case ... which is what I do. But on the other hand, LSI didn't do
DV in this case either, so the current situation is identical to what we
had previously.
But yes, this type of situation seems quite common. The fusion card HP
sent me initially had this problem, and it does seem to be possible to
upgrade all the problem cards, so reporting the issue and recommending
an upgrade seems to be a good approach.
James
next prev parent reply other threads:[~2005-08-09 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 21:46 [PATCH] SPI transport class and generic Domain Validation for fusion James Bottomley
2005-08-09 9:13 ` Christoph Hellwig
2005-08-09 14:47 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 0:07 Moore, Eric Dean
2005-08-09 2:19 ` James Bottomley
2005-08-12 15:12 ` James Bottomley
2005-08-09 19:03 Moore, Eric Dean
2005-08-09 19:09 ` James Bottomley
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=1123598830.5170.19.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Eric.Moore@lsil.com \
--cc=hch@infradead.org \
--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