From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [patch 6/8] mptfusion: fc transport
Date: 25 Nov 2004 14:54:32 -0600 [thread overview]
Message-ID: <1101416079.1717.26.camel@mulgrave> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C5468AD@nacos172.co.lsil.com>
On Fri, 2004-11-19 at 09:39, Moore, Eric Dean wrote:
> This provides fc_transport support, exporting
> port_id, port_name, node_name.
This:
@@ -4,6 +4,7 @@
config FUSION
tristate "Fusion MPT (base + ScsiHost) drivers"
depends on PCI && SCSI
+ select SCSI_FC_ATTRS
---help---
Doesn't look correct. It will force the FC attrs to be built even if
you're only building for a purely SPI device. Worse, module
dependencies will force the FC transport to load even if you're only
attaching to a SCSI device. This isn't really optimal, especially as
the FC transport class is growing in size now.
How difficult would it be to separate out the scsi and FC pieces of the
fusion driver, so we could allow more fined grained control of this?
James
next prev parent reply other threads:[~2004-11-26 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 15:39 [patch 6/8] mptfusion: fc transport Moore, Eric Dean
2004-11-25 20:54 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 19:14 Moore, Eric Dean
2004-12-07 0:29 Moore, Eric Dean
2005-01-08 21:33 ` James Bottomley
2004-12-06 17:12 Moore, Eric Dean
2004-12-06 17:20 ` James Bottomley
2004-12-03 17:33 Moore, Eric Dean
2004-12-03 18:17 ` Christoph Hellwig
2004-12-06 15:18 ` James Bottomley
2004-12-01 23:40 Moore, Eric Dean
2004-12-01 19:46 Moore, Eric Dean
2004-12-01 20:49 ` James Bottomley
2004-11-18 23:33 Moore, Eric Dean
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=1101416079.1717.26.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Eric.Moore@lsil.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