All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: trenn@suse.de
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Miles Lane <miles.lane@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq.c:(.text+0xaf178): undefined reference to	`cpufreq_gov_performance'
Date: Thu, 02 Aug 2007 14:04:05 +0200	[thread overview]
Message-ID: <46B1C835.3060505@googlemail.com> (raw)
In-Reply-To: <1186053332.18821.465.camel@queen.suse.de>

Thomas Renninger wrote:
> On Wed, 2007-08-01 at 16:57 -0700, Andrew Morton wrote:
>> 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.
> 
> Miles, could you send me or point me to the offending .config file.

http://lkml.org/lkml/2007/8/1/480

> 
> Thanks,
> 
>    Thomas


Gabriel

      reply	other threads:[~2007-08-02 12:04 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
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 [this message]

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=46B1C835.3060505@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=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 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.