From: Brett Russ <russb@emc.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: libata-dev queue, ATA passthru updated
Date: Wed, 22 Jun 2005 16:22:30 -0400 [thread overview]
Message-ID: <42B9C886.6010106@emc.com> (raw)
In-Reply-To: <42B9C616.9030101@pobox.com>
Jeff Garzik wrote:
>
> I have updated the 'chs-support' and 'passthru' branches of
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> to be current for the latest kernel.
>
> Additionally, I have uploaded the contents of the 'passthru' branch as a
> patch, at
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.12-git4-passthru1.patch.bz2
Wasn't T10 supposed to standardize passthru at the March meeting? Any idea when this can go mainstream?
BR
next prev parent reply other threads:[~2005-06-22 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 20:12 libata-dev queue, ATA passthru updated Jeff Garzik
2005-06-22 20:22 ` Brett Russ [this message]
2005-06-22 20:33 ` Jeff Garzik
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=42B9C886.6010106@emc.com \
--to=russb@emc.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).