From: Mattia Dongili <malattia@linux.it>
To: alex1000@comcast.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Error compiling 2.6.19rc[56]
Date: Fri, 17 Nov 2006 20:37:49 +0100 [thread overview]
Message-ID: <20061117193749.GC12979@inferi.kami.home> (raw)
In-Reply-To: <111720061810.16287.455DFAF8000E320600003F9F2207021573CFCFCFCE980A040E@comcast.net>
On Fri, Nov 17, 2006 at 06:10:01PM +0000, alex1000@comcast.net wrote:
> I get the following error when attempting to compile 2.6.19rc[56]
>
> drivers/built-in.o(.text+0x7ef32): In function `powersave_bias_target':
> : undefined reference to `cpufreq_frequency_table_target'
> drivers/built-in.o(.text+0x7ef7d): In function `powersave_bias_target':
> : undefined reference to `cpufreq_frequency_table_target'
> drivers/built-in.o(.text+0x7efb3): In function `powersave_bias_target':
> : undefined reference to `cpufreq_frequency_table_target'
> drivers/built-in.o(.text+0x7f056): In function `ondemand_powersave_bias_init':
> : undefined reference to `cpufreq_frequency_get_table'
> make: *** [.tmp_vmlinux1] Error 1
I just sent this to the CPUFreq mailing list.
Allow CONFIG_CPU_FREQ_GOV_ONDEMAND=y
Signed-off-by: Mattia Dongili <malattia@linux.it>
---
diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
index 2cc71b6..491779a 100644
--- a/drivers/cpufreq/Kconfig
+++ b/drivers/cpufreq/Kconfig
@@ -107,6 +107,7 @@ config CPU_FREQ_GOV_USERSPACE
config CPU_FREQ_GOV_ONDEMAND
tristate "'ondemand' cpufreq policy governor"
+ select CPU_FREQ_TABLE
help
'ondemand' - This driver adds a dynamic cpufreq policy governor.
The governor does a periodic polling and
next prev parent reply other threads:[~2006-11-17 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 18:10 alex1000
2006-11-17 19:37 ` Mattia Dongili [this message]
2006-11-17 18:47 alex1000
2006-11-17 22:46 alex1000
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=20061117193749.GC12979@inferi.kami.home \
--to=malattia@linux.it \
--cc=alex1000@comcast.net \
--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
all inboxes | Powered by JetHome®