From: "Adam J. Richter" <adam@yggdrasil.com>
To: linux@brodo.de, rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.64-bk[2-4]: CONFIG_CPU_FREQ_24_API breaks kernel/cpufreq.c compile
Date: Sun, 9 Mar 2003 11:17:29 -0800 [thread overview]
Message-ID: <200303091917.LAA02587@adam.yggdrasil.com> (raw)
linux-2.5.64-bk2 added the following lines to
cpufreq_add_dev in kernel/cpufreq.c:
#ifdef CONFIG_CPU_FREQ_24_API
cpu_min_freq[cpu] = cpufreq_driver->policy[cpu].cpuinfo.min_freq;
cpu_max_freq[cpu] = cpufreq_driver->policy[cpu].cpuinfo.max_freq;
cpu_cur_freq[cpu] = cpufreq_driver->cpu_cur_freq[cpu];
#endif
However, cpu_{min,max,cur}_freq are static variables in
drivers/cpufreq/userspace.c. Making the variables global is not a
sufficient fix, because drivers/cpufreq/userspace.c can be built as
separate module. So, I guess the variables should be moved to
kernel/cpufreq.c or the code that I quoted above should somehow be
moved.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
next reply other threads:[~2003-03-09 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 19:17 Adam J. Richter [this message]
2003-03-09 19:35 ` Russell King
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=200303091917.LAA02587@adam.yggdrasil.com \
--to=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®