From: Rusty Lynch <rusty@linux.co.intel.com>
To: andrew.grover@intel.com
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH][TRIVIAL] ACPI_PROCESSOR depends on CPU_FREQ
Date: 06 Feb 2003 13:28:11 -0800 [thread overview]
Message-ID: <1044566892.3098.19.camel@vmhack> (raw)
After pulling from Linus's tree my build broke while attempting to
compile drivers/acpi/processor.c because cpufreq_get_policy() and
cpufreq_set_policy() were not defined.
Here is a quick Kconfig fix.
--rustyl
--- drivers/acpi/Kconfig.orig 2003-02-06 13:29:24.000000000 -0800
+++ drivers/acpi/Kconfig 2003-02-06 13:31:01.000000000 -0800
@@ -110,6 +110,7 @@
config ACPI_PROCESSOR
tristate "Processor"
+ depends on CPU_FREQ
depends on IA64 && !IA64_HP_SIM || X86 && ACPI && !ACPI_HT_ONLY
help
This driver installs ACPI as the idle handler for Linux, and uses
next reply other threads:[~2003-02-06 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 21:28 Rusty Lynch [this message]
[not found] <200302062142.h16LgaF20694@caduceus.jf.intel.com>
2003-02-06 21:46 ` [PATCH][TRIVIAL] ACPI_PROCESSOR depends on CPU_FREQ Rusty Lynch
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=1044566892.3098.19.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=andrew.grover@intel.com \
--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