From: Dominik Brodowski <linux@brodo.de>
To: Miles Lane <miles.lane@comcast.net>
Cc: linux-kernel@vger.kernel.org, paulus@au.ibm.com,
benh@kernel.crashing.org
Subject: Re: 2.6.0-test1-ac2 -- arch/ppc/platforms/pmac_cpufreq.c:179: `CPUFREQ_ALL_CPUS' undeclared (first use in this function)
Date: Sat, 19 Jul 2003 22:32:48 +0200 [thread overview]
Message-ID: <20030719203248.GB731@brodo.de> (raw)
In-Reply-To: <200307191244.31830.miles.lane@comcast.net>
On Sat, Jul 19, 2003 at 12:44:31PM -0700, Miles Lane wrote:
> CC arch/ppc/platforms/pmac_cpufreq.o
> arch/ppc/platforms/pmac_cpufreq.c: In function `do_set_cpu_speed':
> arch/ppc/platforms/pmac_cpufreq.c: 179: `CPUFREQ_ALL_CPUS' undeclared (first
>
> use in this function)
>
> CONFIG_CPU_FREQ=y
> CONFIG_CPU_FREQ_PROC_INTF=y
> CONFIG_CPU_FREQ_24_API=y
> CONFIG_CPU_FREQ_PMAC=y
Intermediate fix [replace CPUFREQ_ALL_CPUS with either 0 or
smp_processor_id() ] for this is already in Linus' tree, important update
for the pmac-cpufreq driver is in benh's tree and will hopefully be pushed
to Linus tree soon.
Dominik
prev parent reply other threads:[~2003-07-19 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 19:44 2.6.0-test1-ac2 -- arch/ppc/platforms/pmac_cpufreq.c:179: `CPUFREQ_ALL_CPUS' undeclared (first use in this function) Miles Lane
2003-07-19 20:32 ` Dominik Brodowski [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=20030719203248.GB731@brodo.de \
--to=linux@brodo.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@comcast.net \
--cc=paulus@au.ibm.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 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).