Linux-Next discussions
 help / color / mirror / Atom feed
From: Eric Paris <eparis@parisplace.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Dave Jones <davej@redhat.com>, Avi Kivity <avi@redhat.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	cpufreq@vger.kernel.org
Subject: Re: [PATCH -next] cpufreq: provide cpufreq_get stub
Date: Tue, 6 Oct 2009 16:29:01 -0400	[thread overview]
Message-ID: <7e0fb38c0910061329x54b90f8djb2db59ce6152c19e@mail.gmail.com> (raw)
In-Reply-To: <20091006110211.139b91e5.randy.dunlap@oracle.com>

On Tue, Oct 6, 2009 at 2:02 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> When CONFIG_CPU_FREQ is disabled, cpufreq_get() needs a stub.
> Used by kvm (although it looks like a bit of the kvm code could
> be omitted when CONFIG_CPU_FREQ is disabled).
>
> arch/x86/built-in.o: In function `kvm_arch_init':
> (.text+0x10de7): undefined reference to `cpufreq_get'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>

It does what it says it does and gives me a building kernel again.

Tested-by: Eric Paris <eparis@redhat.com>

  reply	other threads:[~2009-10-06 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  5:52 linux-next: Tree for October 6 Stephen Rothwell
2009-10-06 18:02 ` [PATCH -next] cpufreq: provide cpufreq_get stub Randy Dunlap
2009-10-06 20:29   ` Eric Paris [this message]
2009-10-06 20:27 ` [PATCH -next] wireless: fix CFG80211_WEXT build problems Randy Dunlap
2009-10-06 21:33   ` Johannes Berg

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=7e0fb38c0910061329x54b90f8djb2db59ce6152c19e@mail.gmail.com \
    --to=eparis@parisplace.org \
    --cc=avi@redhat.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox