From: Dave Jones <davej@suse.de>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: Juliusz Chroboczek <jch@pps.jussieu.fr>, cpufreq@www.linux.org.uk
Subject: Re: Cpufreq: powernow-k7 weirdness
Date: Mon, 7 Jul 2003 19:32:52 +0200 [thread overview]
Message-ID: <20030707193252.A9758@suse.de> (raw)
In-Reply-To: <20030707133240.GD7796@poupinou.org>; from ducrot@poupinou.org on Mon, Jul 07, 2003 at 03:32:40PM +0200
On Mon, Jul 07, 2003 at 03:32:40PM +0200, Ducrot Bruno wrote:
> On Mon, Jul 07, 2003 at 02:58:37PM +0200, Juliusz Chroboczek wrote:
> > >> Running stock 2.5.73 (ACPI + preempt) on a Compaq Presario 711, CPU is
> > >> a 950MHz mobile Duron. I'm getting unexpected timings when enabling
> > >> cpufreq.
> >
> > > There is a little bug in powernow-k7.c
> >
> > > ducrot@neptune $ cvs diff -u -r1.42 powernow-k7.c
> >
> > Yep, that did it. Thanks a lot.
> >
> > Why don't you push it into 2.5?
>
> Well, I supposed it was in linus bk tree. I will report then.
It's in my cpufreq bitkeeper tree waiting for Linus to pull
from for about a week. I've been a little preoccupied this weekend
getting married, so I'll ask him to pull when I get back.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2003-07-07 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 1:00 Cpufreq: powernow-k7 weirdness Juliusz Chroboczek
2003-07-06 1:21 ` Ducrot Bruno
2003-07-06 17:11 ` Carl Thompson
2003-07-06 17:28 ` Jay Goodman Tamboli
2003-07-06 17:43 ` Carl Thompson
2003-07-06 18:48 ` Ducrot Bruno
2003-07-06 21:56 ` Luigi Belli
2003-07-07 4:16 ` Michael Frank
2003-07-07 13:12 ` Ducrot Bruno
2003-07-07 15:06 ` Michael Frank
2003-07-07 16:32 ` Daniel Thor Kristjansson
2003-07-07 12:58 ` Juliusz Chroboczek
2003-07-07 13:32 ` Ducrot Bruno
2003-07-07 17:32 ` Dave Jones [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=20030707193252.A9758@suse.de \
--to=davej@suse.de \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=jch@pps.jussieu.fr \
/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