From: Brian King <brking@us.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata/sas patches
Date: Mon, 22 May 2006 14:18:25 -0500 [thread overview]
Message-ID: <44720E81.8020609@us.ibm.com> (raw)
In-Reply-To: <4471F34F.2040600@garzik.org>
Jeff Garzik wrote:
> Brian King wrote:
>> I just uploaded my updated libata patchset to support attaching
>> SATA devices to SAS HBAs. It's only lightly tested at this point.
>> I still need to give it another review myself and make sure
>> I'm happy with all the error cases, but the base function
>> is working for me, so I figured I'd post the link. I'll
>> hopefully submit the code to the list soon.
>>
>> http://prdownloads.sourceforge.net/iprdd/ipr-sata.tgz?download
>
> Are you gonna be at the storage summit? They are going to discuss
> SAS/SATA integration there.
>
> I won't be there, alas...
Yes. I will be there. Too bad you can't make it.
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
prev parent reply other threads:[~2006-05-22 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 14:35 libata/sas patches Brian King
2006-05-22 17:22 ` Jeff Garzik
2006-05-22 19:18 ` Brian King [this message]
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=44720E81.8020609@us.ibm.com \
--to=brking@us.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).