linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Brett Russ <russb@emc.com>
Cc: linux-ide@vger.kernel.org, ric@emc.com
Subject: Re: [PATCH] Re: AHCI: support for tf_read (RFC)
Date: Thu, 10 Mar 2005 13:32:22 -0500	[thread overview]
Message-ID: <423092B6.1050106@pobox.com> (raw)
In-Reply-To: <42307AF0.4030309@emc.com>

Brett Russ wrote:
> Jeff Garzik wrote:
> 
>> I checked the attached patch into a local repository, but haven't yet 
>> merged it into libata-dev-2.6, or tested it.
> 
> 
> Jeff,
> 
> The below works for me in testing.  Can you push into libata-2.6?

pulled



      reply	other threads:[~2005-03-10 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 23:24 [PATCH libata-2.6] AHCI: support for tf_read (RFC) Brett Russ
2005-02-24 23:33 ` Jeff Garzik
2005-02-25 23:19 ` [PATCH] " Jeff Garzik
2005-03-07 16:43   ` Brett Russ
2005-03-10 16:50   ` Brett Russ
2005-03-10 18:32     ` Jeff Garzik [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=423092B6.1050106@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=ric@emc.com \
    --cc=russb@emc.com \
    /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).