From: Edd Dumbill <edd@usefulinc.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay.
Date: Wed, 24 Mar 2004 15:59:13 +0000 [thread overview]
Message-ID: <1080143953.15381.61.camel@saag> (raw)
In-Reply-To: <200402252238.55834.ross@datscreative.com.au>
On Wed, 2004-02-25 at 22:38 +1000, Ross Dickson wrote:
> Patches attached rediffed for 2.6.3 and 2.6.3-mm3.
I've been running the idleC1halt patch against 2.6.3 and 2.6.4 for some
time and have had no crashes and no clock skew. A7N8X Delux mobo, AMD
Athlon XP 3000+.
Thanks for your work.
-- Edd
prev parent reply other threads:[~2004-03-24 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:22 [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-12 18:17 ` Derek Foreman
2004-02-12 16:11 ` Daniel Drake
2004-02-12 19:30 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaroundinstead " Carlos Silva
2004-02-12 19:54 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead " Derek Foreman
2004-02-12 21:44 ` Jesse Allen
2004-02-12 21:52 ` Derek Foreman
2004-02-12 22:06 ` Craig Bradney
2004-02-12 23:04 ` Jesse Allen
2004-02-12 23:15 ` Craig Bradney
2004-02-12 23:37 ` Jesse Allen
2004-02-12 23:50 ` Craig Bradney
2004-02-12 23:20 ` Roberto Sanchez
2004-02-13 11:17 ` Prakash K. Cheemplavam
2004-02-13 14:41 ` Ross Dickson
2004-02-13 15:55 ` Nforce2, APIC, CPU Disconnect and setup_boot_APIC_clock() cheuche+lkml
2004-02-14 1:24 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Ross Dickson
2004-02-14 4:46 ` GCC feature request: warn on "if (function_name)" Jamie Lokier
2004-02-14 4:51 ` Andrew Pinski
2004-02-14 11:16 ` [PATCH] 2.6, 2.4, Nforce2, Experimental idle halt workaround instead of apic ack delay Prakash K. Cheemplavam
2004-02-14 16:13 ` Ross Dickson
2004-02-14 21:46 ` Ian Kumlien
2004-02-23 1:33 ` Prakash K. Cheemplavam
2004-02-23 19:50 ` Jesse Allen
2004-02-23 1:37 ` Prakash K. Cheemplavam
2004-02-25 12:38 ` Ross Dickson
2004-02-25 19:49 ` Prakash K. Cheemplavam
2004-02-25 21:44 ` Arjen Verweij
2004-02-26 0:13 ` Ross Dickson
2004-02-26 9:59 ` Mikael Pettersson
2004-03-07 14:46 ` Craig Bradney
2004-03-08 22:42 ` Arjen Verweij
2004-03-08 22:59 ` Craig Bradney
2004-03-08 23:11 ` Arjen Verweij
2004-03-14 12:04 ` Arjen Verweij
2004-03-09 18:38 ` Josh McKinney
2004-03-24 15:59 ` Edd Dumbill [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=1080143953.15381.61.camel@saag \
--to=edd@usefulinc.com \
--cc=linux-kernel@vger.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.