From: Brian King <brking@us.ibm.com>
To: Brian King <brking@us.ibm.com>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org,
jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] ipr: Support attaching SATA devices
Date: Wed, 09 Aug 2006 10:27:07 -0500 [thread overview]
Message-ID: <44D9FECB.3080004@us.ibm.com> (raw)
In-Reply-To: <200608091522.k79FMON6004111@d01av01.pok.ibm.com>
James,
This patch depends on the SAS libata API that was just recently
added to Jeff's #upstream branch. Should I resend this patch once
the libata changes are upstream?
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2006-08-09 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:22 [PATCH 1/1] ipr: Support attaching SATA devices Brian King
2006-08-09 15:27 ` Brian King [this message]
2006-08-16 17:58 ` [PATCH 1/1] ipr: Support attaching SATA devices - drop Brian King
-- strict thread matches above, loose matches on Subject: below --
2006-09-25 17:39 [PATCH 1/1] ipr: Support attaching SATA devices Brian King
2006-09-25 20:35 ` James Bottomley
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=44D9FECB.3080004@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Bottomley@steeleye.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).