From: Douglas Gilbert <dougg@torque.net>
To: brking@us.ibm.com
Cc: jgarzik@pobox.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
'SCSI Mailing List' <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [PATCH 0/6] libata: Support SATA attached via SAS
Date: Wed, 07 Jun 2006 23:49:06 -0400 [thread overview]
Message-ID: <44879E32.1020500@torque.net> (raw)
In-Reply-To: <4486FDBD.9030200@us.ibm.com>
Brian King wrote:
> Jeff,
>
> Here is a refresh of my patchset to allow SAS HBAs to use libata to
> control attached SATA devices. It should apply cleanly to #upstream.
Brian,
I hope that libata's ATA PASS THROUGH (16) SCSI command
is wired up as I just checked a new device type '-d sat'
into smartmontools cvs.
Doug Gilbert
next prev parent reply other threads:[~2006-06-08 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:24 [PATCH 0/6] libata: Support SATA attached via SAS Brian King
2006-06-07 17:09 ` Douglas Gilbert
2006-06-07 17:56 ` Brian King
2006-06-08 3:49 ` Douglas Gilbert [this message]
2006-06-08 13:32 ` 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=44879E32.1020500@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@steeleye.com \
--cc=brking@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).