From: Brian King <brking@us.ibm.com>
To: Luben Tuikov <luben_tuikov@adaptec.com>
Cc: Tom Duffy <tduffy@sun.com>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
"Moore, Eric Dean" <Eric.Moore@lsil.com>
Subject: Re: SAS transport class status?
Date: Fri, 29 Jul 2005 08:51:13 -0500 [thread overview]
Message-ID: <42EA3451.9010908@us.ibm.com> (raw)
In-Reply-To: <42E94310.9020604@adaptec.com>
Luben Tuikov wrote:
> On 07/28/05 16:27, Tom Duffy wrote:
>
>>Luben, et. al.
>>
>>Any updates on the SAS transport class code? Are we likely to see this
>>happening in the 2.6.14 time frame? After the BOF at OLS, I figured we
>>would be moving quick on this...
>
>
> It really depends on when 2.6.14 is coming out.
> I'm doing discovery at the moment.
Luben, are you also working on the PHY transport class James mentions in
his OLS paper, or have you been focusing just on the SAS transport class?
Thanks
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2005-07-29 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:27 SAS transport class status? Tom Duffy
2005-07-28 20:41 ` Luben Tuikov
2005-07-29 13:51 ` Brian King [this message]
2005-07-29 14:43 ` Luben Tuikov
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=42EA3451.9010908@us.ibm.com \
--to=brking@us.ibm.com \
--cc=Eric.Moore@lsil.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=tduffy@sun.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