From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
lenb@kernel.org, cpufreq@vger.kernel.org,
akpm <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, davej@redhat.com
Subject: [PATCH -next] x86/cpufreq: don't use acpi_processor_get_bios_limit when not available
Date: Mon, 16 Nov 2009 15:32:42 -0800 [thread overview]
Message-ID: <20091116153242.3c194a5a.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091116181453.b42247cf.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
Only reference this function when the kconfig makes it available.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
arch/x86/kernel/cpu/cpufreq/powernow-k7.c | 2 ++
1 file changed, 2 insertions(+)
--- linux-next-20091113.orig/arch/x86/kernel/cpu/cpufreq/powernow-k7.c
+++ linux-next-20091113/arch/x86/kernel/cpu/cpufreq/powernow-k7.c
@@ -717,7 +717,9 @@ static struct cpufreq_driver powernow_dr
.verify = powernow_verify,
.target = powernow_target,
.get = powernow_get,
+#ifdef CONFIG_X86_POWERNOW_K7_ACPI
.bios_limit = acpi_processor_get_bios_limit,
+#endif
.init = powernow_cpu_init,
.exit = powernow_cpu_exit,
.name = "powernow-k7",
next prev parent reply other threads:[~2009-11-16 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 7:14 linux-next: Tree for November 16 Stephen Rothwell
2009-11-16 14:32 ` Borislav Petkov
2009-11-17 3:19 ` edac-amd tree (Was: Re: linux-next: Tree for November 16) Stephen Rothwell
2009-11-17 12:00 ` Borislav Petkov
2009-11-16 23:32 ` [PATCH -next] acpi: get_bios_limit static inline when CPU_FREQ=n Randy Dunlap
2009-11-16 23:32 ` Randy Dunlap [this message]
2009-11-17 4:36 ` [-next Nov 16] s390 build failure (arch/s390/kernel/time) Sachin Sant
2009-11-17 5:25 ` Stephen Rothwell
2009-11-17 7:59 ` Heiko Carstens
2009-11-17 11:55 ` Sachin Sant
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=20091116153242.3c194a5a.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.