From: Michael Neuling <mikey@neuling.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH] powerpc/cell: fix dependency in cpufreq
Date: Tue, 10 Feb 2009 11:46:52 +1100 [thread overview]
Message-ID: <18282.1234226812@neuling.org> (raw)
cbe_cpufreq.c uses cbe_cpufreq_has_pmi which is provided by
cbe_cpufreq_pmi.c. Hence CBE_CPUFREQ depends on CBE_CPUFREQ_PMI.
Signed-off-by: Michael Neuling <mikey@neuling.org>
---
I'm not 100% sure is this the right fix. Should CBE_CPUFREQ really
depend on CBE_CPUFREQ_PMI?
arch/powerpc/platforms/cell/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6-ozlabs/arch/powerpc/platforms/cell/Kconfig
===================================================================
--- linux-2.6-ozlabs.orig/arch/powerpc/platforms/cell/Kconfig
+++ linux-2.6-ozlabs/arch/powerpc/platforms/cell/Kconfig
@@ -111,7 +111,7 @@ config CBE_THERM
config CBE_CPUFREQ
tristate "CBE frequency scaling"
- depends on CBE_RAS && CPU_FREQ
+ depends on CBE_RAS && CPU_FREQ && CBE_CPUFREQ_PMI
default m
help
This adds the cpufreq driver for Cell BE processors.
@@ -120,7 +120,7 @@ config CBE_CPUFREQ
config CBE_CPUFREQ_PMI
tristate "CBE frequency scaling using PMI interface"
- depends on CBE_CPUFREQ && PPC_PMI && EXPERIMENTAL
+ depends on PPC_PMI && EXPERIMENTAL
default n
help
Select this, if you want to use the PMI interface
next reply other threads:[~2009-02-10 0:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 0:46 Michael Neuling [this message]
2009-02-10 1:01 ` [PATCH] powerpc/cell: fix dependency in cpufreq Michael Ellerman
2009-02-10 1:48 ` Michael Neuling
2009-02-10 2:01 ` Michael Neuling
2009-02-10 15:55 ` Arnd Bergmann
2009-02-10 22:27 ` Michael Neuling
2009-02-10 6:51 ` Michael Neuling
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=18282.1234226812@neuling.org \
--to=mikey@neuling.org \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.