From: Jeff Garzik <jeff@garzik.org>
To: brking@us.ibm.com
Cc: linux-ide@vger.kernel.org
Subject: Re: libata/sas patches
Date: Mon, 22 May 2006 13:22:23 -0400 [thread overview]
Message-ID: <4471F34F.2040600@garzik.org> (raw)
In-Reply-To: <4471CC15.8000102@us.ibm.com>
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...
Jeff
next prev parent reply other threads:[~2006-05-22 17:23 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 [this message]
2006-05-22 19:18 ` Brian King
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=4471F34F.2040600@garzik.org \
--to=jeff@garzik.org \
--cc=brking@us.ibm.com \
--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).