From: Len Brown <lenb@kernel.org>
To: linux-pm@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: [PATCH 3/5] intel_idle: disable module support
Date: Sun, 15 Aug 2010 01:22:03 -0400 [thread overview]
Message-ID: <6ce9cd8669fa1195fdc21643370e34523c7ac988.1281849655.git.len.brown@intel.com> (raw)
In-Reply-To: <1281849725-7379-1-git-send-email-lenb@kernel.org>
In-Reply-To: <0394c6676e3fa48587fbe4821390d3264672c530.1281849655.git.len.brown@intel.com>
From: Len Brown <len.brown@intel.com>
Right now the module capability is cauing more trouble
than it is worth. At least one distro built intel_idle as a module
where it lost the init race with ACPI, making it useless.
Make intel_idle bool so that if you select it, you will use it.
We can restore module capability after cpuidle is enhanced
to handle run-time changing of idle drivers.
Signed-off-by: Len Brown <len.brown@intel.com>
---
drivers/idle/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/idle/Kconfig b/drivers/idle/Kconfig
index fb5c518..82e4e86 100644
--- a/drivers/idle/Kconfig
+++ b/drivers/idle/Kconfig
@@ -1,5 +1,5 @@
config INTEL_IDLE
- tristate "Cpuidle Driver for Intel Processors"
+ bool "Cpuidle Driver for Intel Processors"
depends on CPU_IDLE
depends on X86
depends on CPU_SUP_INTEL
--
1.7.2.1.95.g3d045
next prev parent reply other threads:[~2010-08-15 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 5:22 idle patches for 2.6.36.merge Len Brown
2010-08-15 5:22 ` [PATCH 1/5] intel_idle: delete power_policy modparam, and choose substate functions Len Brown
2010-08-15 5:22 ` [PATCH 2/5] intel_idle: add support for Westmere-EX Len Brown
2010-08-15 5:22 ` Len Brown [this message]
2010-08-15 5:22 ` [PATCH 4/5] intel_idle: no longer EXPERIMENTAL Len Brown
2010-08-15 5:22 ` [PATCH 5/5] intel_idle: recognize Lincroft Atom Processor Len Brown
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=6ce9cd8669fa1195fdc21643370e34523c7ac988.1281849655.git.len.brown@intel.com \
--to=lenb@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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®