From: Mark Lord <kernel@teksavvy.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [upstream-next] ahci start engine
Date: Wed, 26 Oct 2011 19:40:21 -0400 [thread overview]
Message-ID: <4EA89A65.6010406@teksavvy.com> (raw)
In-Reply-To: <CAN8TOE_m07dirv+ZJ4FuePEipyXWH3B8NJQ+1ag=E5iyJMUXaw@mail.gmail.com>
On 11-10-24 07:43 PM, Brian Norris wrote:
> On Fri, Oct 21, 2011 at 3:38 PM, Jeff Garzik <jgarzik@pobox.com> wrote:
>> On 10/21/2011 06:27 PM, Brian Norris wrote:
>>> 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
>>
>> 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.
>
> Thanks, that'd be great.
Ditto. That bug bites me here all of the time now.
next prev parent reply other threads:[~2011-10-26 23:40 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
2011-10-24 23:43 ` Brian Norris
2011-10-26 23:40 ` Mark Lord [this message]
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=4EA89A65.6010406@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=computersforpeace@gmail.com \
--cc=jgarzik@pobox.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 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).