From: Jeff Garzik <jgarzik@pobox.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, Tejun Heo <htejun@gmail.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
thlin@linux.vnet.ibm.com
Subject: Re: Recent ipr breakage (ata_do_eh api change)
Date: Fri, 04 May 2007 11:21:57 -0400 [thread overview]
Message-ID: <463B4F95.5080307@pobox.com> (raw)
In-Reply-To: <463B4DF4.70908@linux.vnet.ibm.com>
Brian King wrote:
> This looks like a fix for a compile problem with the libata-all
> branch. I did some poking around and it looks like the ata_do_eh
> api change is in Jeff's #all branch, but not in #upstream, so
> I am assuming the ipr patch mentioned above should be reverted
> in mainline for now.
At the moment, there is no #upstream branch. It's all, um, upstream :)
What you see in #ALL is the combination of #reset-seq and #mv-ahci branches.
Jeff
prev parent reply other threads:[~2007-05-04 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 15:15 Recent ipr breakage (ata_do_eh api change) Brian King
2007-05-04 15:21 ` 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=463B4F95.5080307@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=brking@linux.vnet.ibm.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=thlin@linux.vnet.ibm.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).