public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Thomas Renninger <trenn@suse.de>
Subject: Re: cpufreq.c:(.text+0xaf178): undefined reference to `cpufreq_gov_performance'
Date: Wed, 1 Aug 2007 16:57:04 -0700	[thread overview]
Message-ID: <20070801165704.a26961b7.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0708011631k7f476af2jcd01d2875f4b4b17@mail.gmail.com>

On Wed, 1 Aug 2007 16:31:46 -0700
"Miles Lane" <miles.lane@gmail.com> wrote:

>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `__cpufreq_governor':
> cpufreq.c:(.text+0xaf178): undefined reference to `cpufreq_gov_performance'
> cpufreq.c:(.text+0xaf18a): undefined reference to `cpufreq_gov_performance'
> make: *** [.tmp_vmlinux1] Error 1

One for Thomas, I expect.

> # Automatically generated make config: don't edit
> # Linux kernel version: 2.6.23-rc1-mm2
> # Wed Aug  1 15:46:12 2007

<useful thanks.  But snipped>

  reply	other threads:[~2007-08-01 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01 23:31 cpufreq.c:(.text+0xaf178): undefined reference to `cpufreq_gov_performance' Miles Lane
2007-08-01 23:57 ` Andrew Morton [this message]
2007-08-02  0:28   ` Gabriel C
2007-08-02 13:48     ` [-mm patch] CPU_FREQ_GOV_PERFORMANCE must always be y Adrian Bunk
2007-08-02 14:38       ` [-mm patch] CPUfreq: Only check for transition latency on problematic governors Thomas Renninger
2007-08-02 14:54         ` Adrian Bunk
2007-08-02 15:24           ` Thomas Renninger
2007-08-02 11:15   ` cpufreq.c:(.text+0xaf178): undefined reference to `cpufreq_gov_performance' Thomas Renninger
2007-08-02 12:04     ` Gabriel C

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=20070801165704.a26961b7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    --cc=trenn@suse.de \
    /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