From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
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, 9 Aug 2005 10:13:53 +0100 [thread overview]
Message-ID: <20050809091353.GA11397@infradead.org> (raw)
In-Reply-To: <1123537590.8235.4.camel@mulgrave>
On Mon, Aug 08, 2005 at 04:46:30PM -0500, James Bottomley wrote:
> Eric,
>
> This attached patch should do DV on both physical devices and the
> underlying devices of fusion IM assemblies (providing you apply it on
> top of the prior underlying device exposure patch), which, I believe was
> your only outstanding concern with the last generic DV patch.
>
> There is one slight unsightly piece: the IM device still attaches to the
> transport class however all the parameters it shows actually belong to
> the underlying device at that id ... I could do with finding a way of
> persuading the SPI transport class not to attach to RAID devices.
>
> Since this addresses all of LSI's prior concerns, may I now apply it?
- there's a stale printk("HERE2\n"); in mptscsih_writeSDP1.
- the #undef MPTSCSIH_ENABLE_DOMAIN_VALIDATION is probably not needed
- the hd == NULL check in mptspi_target_alloc isn't needed
- should the driver print a warning about too old firmware when we can't
access page 0?
next prev parent reply other threads:[~2005-08-09 9:14 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 [this message]
2005-08-09 14:47 ` James Bottomley
-- 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=20050809091353.GA11397@infradead.org \
--to=hch@infradead.org \
--cc=Eric.Moore@lsil.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