From: Patrick Mansfield <patmans@us.ibm.com>
To: Martin Hicks <mort@wildopensource.com>
Cc: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: Transport Attributes -- attempt#4
Date: Tue, 20 Jan 2004 15:48:01 -0800 [thread overview]
Message-ID: <20040120154801.B25713@beaverton.ibm.com> (raw)
In-Reply-To: <20040120215645.GG15871@localhost>; from mort@wildopensource.com on Tue, Jan 20, 2004 at 04:56:45PM -0500
On Tue, Jan 20, 2004 at 04:56:45PM -0500, Martin Hicks wrote:
>
> Hi again,
>
> Updated patches against Linus' bk tree from earlier today. The patch
> that fixes up the scsi_sysfs.c error path, that was sent out by me on
> Jan 16, is required for the core patch to apply cleanly.
>
> I think I've addressed all the comments from the last round with the
> exception of doing Lazy registration of the transport classes. I'm
> still not totally convinced that this is really required.
It's certainly are not required, but makes it easier to add other
transports, and is in line with allocating resources as needed. Making
them modules means the code is only loaded when required by an adapter, it
is not always loaded with scsi core.
We could potentially have iSCSI and maybe others per SCSI standards. Then
we have USB, ieee1394, and raid cards that might want to add their own bus
and attributes, though these ones might more easily add them via scsi_host
attributes.
-- Patrick Mansfield
next prev parent reply other threads:[~2004-01-20 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 21:56 Transport Attributes -- attempt#4 Martin Hicks
2004-01-20 23:48 ` Patrick Mansfield [this message]
2004-02-24 0:17 ` James Bottomley
2004-02-24 5:58 ` Jeremy Higdon
2004-02-24 15:02 ` James Bottomley
2004-02-25 7:08 ` Jeremy Higdon
2004-02-25 16:42 ` James Bottomley
2004-03-04 16:14 ` Martin Hicks
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=20040120154801.B25713@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mort@wildopensource.com \
/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