From: Dave Jones <davej@codemonkey.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: Matt Reppert <repp0017@tc.umn.edu>, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.0-test1
Date: Tue, 15 Jul 2003 19:11:01 +0100 [thread overview]
Message-ID: <20030715181100.GF15505@suse.de> (raw)
In-Reply-To: <20030715173844.GB1950@brodo.de>
On Tue, Jul 15, 2003 at 07:38:44PM +0200, Dominik Brodowski wrote:
> No, please don't do this. There is no function at all in the cpufreq core
> which may be called with CPUFREQ_ALL_CPUS as arguments. Well, there had
> been, many months ago. But it really shall not be defined or used anywhere
> outside the 2.4. proc-intf any more.
ick, you're right of course.
> Now, wrt the ppc-cpufreq driver: benh's 2.5. tree includes a much more
> updated version than plain 2.6.0-test1 -- Ben, can you push that to Linus,
> please? Also, please change the line
> freqs.cpu = CPUFREQ_ALL_CPUS;
> in do_set_cpu_speed() to
> freqs.cpu = 0;
> which is the way it should be done now.
Ok, CPUFREQ_ALL_CPUS is no more in my pending tree.
Documentation/cpu-freq/core.txt is also out of date and could use
an update, but I'm not sure if its just that define thats out of date.
Care to give it a read through?
Dave
next prev parent reply other threads:[~2003-07-15 17:58 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 3:59 Linux v2.6.0-test1 Linus Torvalds
2003-07-14 11:30 ` [trivial] " Jasper Spaans
2003-07-14 15:07 ` 2.6.0-test, how to test it? [Was: Linux v2.6.0-test1] Antonio Vargas
2003-07-14 20:08 ` Linux v2.6.0-test1 (compile stats) John Cherry
2003-07-15 4:11 ` Linux v2.6.0-test1 Matt Reppert
2003-07-15 10:56 ` Dave Jones
2003-07-15 17:38 ` Dominik Brodowski
2003-07-15 18:11 ` Dave Jones [this message]
2003-07-16 1:29 ` Hotplug Oops " Mike Fedyk
2003-07-16 1:37 ` Greg KH
2003-07-16 1:46 ` Mike Fedyk
2003-07-16 2:31 ` Greg KH
2003-07-16 20:15 ` Mike Fedyk
2003-07-16 20:26 ` Mike Fedyk
2003-07-18 2:31 ` Greg KH
2003-07-18 18:45 ` Mike Fedyk
2003-07-29 18:02 ` Mike Fedyk
2003-07-29 19:00 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 7:52 Dirk Meul
2003-07-16 6:32 ` Martin Schlemmer
2003-07-14 11:50 John Bradford
2003-07-14 11:53 ` Dave Jones
2003-07-14 12:00 ` William Lee Irwin III
2003-07-14 12:39 ` Alan Cox
2003-07-14 12:47 ` William Lee Irwin III
2003-07-14 12:47 ` Alan Cox
2003-07-14 12:40 ` Alan Cox
2003-07-14 16:55 ` Kurt Wall
2003-07-14 11:39 John Bradford
2003-07-14 11:33 ` Alan Cox
2003-07-14 13:56 ` Marcelo Tosatti
2003-07-14 15:07 ` Alan Cox
2003-07-14 16:44 ` Marcelo Tosatti
2003-07-14 11:01 John Bradford
2003-07-14 11:15 ` Alan Cox
2003-05-22 20:12 DMA gone on ALI 1533 Peter
2003-07-14 7:26 ` Linux v2.6.0-test1 Peter
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=20030715181100.GF15505@suse.de \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=repp0017@tc.umn.edu \
/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).