From: James Bottomley <James.Bottomley@steeleye.com>
To: Jeremy Higdon <jeremy@sgi.com>
Cc: Martin Hicks <mort@wildopensource.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Transport Attributes -- attempt#4
Date: 24 Feb 2004 09:02:56 -0600 [thread overview]
Message-ID: <1077634979.1827.7.camel@mulgrave> (raw)
In-Reply-To: <20040224055828.GA503530@sgi.com>
On Mon, 2004-02-23 at 23:58, Jeremy Higdon wrote:
> James, was scsi/scsi_transport.h supposed to be patched also?
> There is a new "size" member of the scsi_transport_template
> structure, but no patch to the data structure itself. Did you
> replace attributes with size?
Well, not really. The patch I provided is a sketch only of what I want
done. It compiles and works on the 53c700 which is where I tested it.
Really, I just want transport and core separated and transport
attributes to be fixed (so there's some way of defining a transport
private API for updating them).
Even with just offset and period as the transport attributes for SPI,
that gives enough to move domain validation out of all the drivers into
the SPI transport layer.
> Also, Martin is on vacation this week, I believe, so he probably
> won't respond until next week.
Yes, I know, It's just that I've been promising to look at this for
weeks, so I didn't want to delay any further.
James
next prev parent reply other threads:[~2004-02-24 15:03 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
2004-02-24 0:17 ` James Bottomley
2004-02-24 5:58 ` Jeremy Higdon
2004-02-24 15:02 ` James Bottomley [this message]
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=1077634979.1827.7.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jeremy@sgi.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