From: "Redeeman" <redeeman@metanurb.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: powernow-k8 havent been tested on preemptive - have now
Date: Sat, 21 Feb 2004 11:08:17 +0100 (CET) [thread overview]
Message-ID: <1271.192.168.1.7.1077358097.squirrel@redeeman.linux.dk> (raw)
In-Reply-To: <20040220230529.GB32153@elf.ucw.cz>
yes, this is how i fixed it myself too, but i thought it would need more
than this. but obviously not.
Greets, Redeeman
> Hi!
>
>> hi, i have been seeing the message that powernow-k8 havent been tested
>> on
>> a preemptive system, for a couple of kernel versions i have been
>> running,
>> and i just want to tell you that it is working absolutely perfect, great
>> job!
>>
>> if there is any questions/comments i would be glad if you would cc them
>> to
>> redeeman@<no-spam>metanurb.dk , thanks!
>
> Okay, in such case we should probably do this:
> Pavel
>
> --- tmp/linux/arch/i386/kernel/cpu/cpufreq/powernow-k8.c 2004-02-21
> 00:04:41.000000000 +0100
> +++ linux/arch/i386/kernel/cpu/cpufreq/powernow-k8.c 2004-02-21
> 00:04:20.000000000 +0100
> @@ -34,10 +34,6 @@
> #define VERSION "version 1.00.08a"
> #include "powernow-k8.h"
>
> -#ifdef CONFIG_PREEMPT
> -#warning this driver has not been tested on a preempt system
> -#endif
> -
> static u32 vstable; /* voltage stabalization time, from PSB, units 20 us
> */
> static u32 plllock; /* pll lock time, from PSB, units 1 us */
> static u32 numps; /* number of p-states, from PSB */
>
>
> --
> When do you have a heart between your knees?
> [Johanka's followup: and *two* hearts?]
>
>
prev parent reply other threads:[~2004-02-21 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 19:05 powernow-k8 havent been tested on preemptive - have now redeeman
2004-02-20 23:05 ` Pavel Machek
2004-02-21 10:08 ` Redeeman [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=1271.192.168.1.7.1077358097.squirrel@redeeman.linux.dk \
--to=redeeman@metanurb.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox