From: Mark Lord <liml@rtr.ca>
To: Erik Slagter <erik@slagter.name>
Cc: Mark Lord <mlord@pobox.com>, Jeff Garzik <jgarzik@pobox.com>,
Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata total system lockup fix
Date: Fri, 19 Aug 2005 09:07:50 -0400 [thread overview]
Message-ID: <4305D9A6.8010502@rtr.ca> (raw)
In-Reply-To: <1124444101.2217.64.camel@localhost.localdomain>
Erik Slagter wrote:
> On Thu, 2005-08-18 at 20:46 -0400, Mark Lord wrote:
>
>>After a week of further experience with this patch,
..
>>I'm now reverting to the original "broken" patch
..
>
> What is exactly the "broken" patch and what is "this" patch?
"this" patch refered to the subject of that email,
the "one-liner" included therein.
The "broken" patch (which behaves in a very unbroken manner)
is in the collection of "essentials" that I maintain for
modern laptop users at http://rtr.ca/dell_i9300/kernels/
Cheers
next prev parent reply other threads:[~2005-08-19 13:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 13:47 libata total system lockup fix Mark Lord
2005-07-25 14:51 ` Jeff Garzik
2005-07-25 15:53 ` Mark Lord
2005-08-05 3:52 ` Tejun Heo
2005-08-05 4:01 ` Tejun Heo
2005-08-11 20:13 ` Jeff Garzik
2005-08-12 0:49 ` Tejun Heo
2005-08-12 2:22 ` Mark Lord
2005-08-12 2:38 ` Tejun Heo
2005-08-12 2:41 ` Tejun Heo
2005-08-09 15:16 ` Mark Lord
2005-08-09 23:54 ` Tejun Heo
2005-08-10 14:16 ` Mark Lord
2005-08-10 21:24 ` Jeff Garzik
2005-08-19 0:46 ` Mark Lord
2005-08-19 3:21 ` Tejun Heo
2005-08-19 3:36 ` Mark Lord
2005-08-19 3:45 ` Tejun Heo
2005-08-19 4:01 ` Mark Lord
2005-08-19 9:37 ` Erik Slagter
2005-08-19 9:35 ` Erik Slagter
2005-08-19 13:07 ` Mark Lord [this message]
2005-08-19 13:32 ` Bartlomiej Zolnierkiewicz
2005-08-19 13:37 ` Bartlomiej Zolnierkiewicz
2005-09-03 22:58 ` Mark Lord
2005-09-03 23:06 ` 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=4305D9A6.8010502@rtr.ca \
--to=liml@rtr.ca \
--cc=erik@slagter.name \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.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 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.