From: Jeff Garzik <jgarzik@pobox.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [upstream-next] ahci start engine
Date: Fri, 21 Oct 2011 18:38:02 -0400 [thread overview]
Message-ID: <4EA1F44A.7020804@pobox.com> (raw)
In-Reply-To: <CAN8TOE8mTWrHOZd08RhZttARGsa74fGmB7f044GHScA87PJcyg@mail.gmail.com>
On 10/21/2011 06:27 PM, Brian Norris wrote:
> Hi Jeff,
>
> If you recall, there was an AHCI hardware bug I was working on a while
> back that Tejun helped me solve (or at least mitigate). In the end, a
> patch was pushed to your libata-dev/upstream-next branch at
> kernel.org. Since then, kernel.org went down (along with your tree). I
> only recently located your new github repository, and I can't find the
> patch anywhere. Has it been dropped? This is the patch header leftover
> in my tree:
>
> commit 936f82ad2254a6712175a36daee9517d6b7a4982
> Author: Tejun Heo<tj@kernel.org>
> Date: Fri Jul 22 11:41:26 2011 +0200
>
> ahci: start engine only during soft/hard resets
>
>
> I can resubmit the entire patch to you if you'd like. I'd appreciate
> it if this could make it upstream soon.
hum, neither that branch nor the patch appears to exist locally; I bet
I accidentally deleted #upstream-next during the move.
Will resuscitate the branch w/ that patch, at github.
Jeff
next prev parent reply other threads:[~2011-10-21 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 22:27 [upstream-next] ahci start engine Brian Norris
2011-10-21 22:38 ` Jeff Garzik [this message]
2011-10-24 23:43 ` Brian Norris
2011-10-26 23:40 ` Mark Lord
2011-11-04 22:54 ` Brian Norris
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=4EA1F44A.7020804@pobox.com \
--to=jgarzik@pobox.com \
--cc=computersforpeace@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.