mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Reuben Farrelly <reuben-linuxkernel@reub.net>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: 2.6.19-rc5-mm1
Date: Wed, 8 Nov 2006 12:05:47 -0800	[thread overview]
Message-ID: <20061108120547.78048229.akpm@osdl.org> (raw)
In-Reply-To: <4551BB5E.6090602@reub.net>

On Wed, 08 Nov 2006 22:11:26 +1100
Reuben Farrelly <reuben-linuxkernel@reub.net> wrote:

> 
> 
> On 8/11/2006 8:54 PM, Andrew Morton wrote:
> > Temporarily at
> > 
> > http://userweb.kernel.org/~akpm/2.6.19-rc5-mm1/
> > 
> > will turn up at
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm1/
> > 
> > 
> > when kernel.org mirroring catches up.
> > 
> > 
> > 
> > - Merged the Kernel-based Virtual Machine patches.  See kvm.sf.net for 
> > userspace tools, instructions, etc.
> > 
> > It needs a recent binutils to build.
> > 
> > - The hrtimer+dynticks code still doesn't work right for machines which halt 
> > their TSC in low-power states.
> 
> I think this might be a davej thing:
> 
>    CC      init/version.o
>    LD      init/built-in.o
>    LD      .tmp_vmlinux1
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_cpu_exit':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:762:
> undefined reference to `cpufreq_frequency_table_put_attr'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_target':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:406:
> undefined reference to `cpufreq_frequency_table_target'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_verify':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:491:
> undefined reference to `cpufreq_frequency_table_verify'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_cpu_init':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:698:
> undefined reference to `cpufreq_frequency_table_cpuinfo'
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:734:
> undefined reference to `cpufreq_frequency_table_get_attr'
> arch/x86_64/kernel/built-in.o: In function `trampoline_end':
> (.data+0x40c0): undefined reference to `cpufreq_freq_attr_scaling_available_freqs'
> drivers/built-in.o: In function `ondemand_powersave_bias_init':
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:164: undefined
> reference to `cpufreq_frequency_get_table'
> drivers/built-in.o: In function `powersave_bias_target':
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:126: undefined
> reference to `cpufreq_frequency_table_target'
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:134: undefined
> reference to `cpufreq_frequency_table_target'
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:138: undefined
> reference to `cpufreq_frequency_table_target'
> make: *** [.tmp_vmlinux1] Error 1
> [root@tornado linux-mm]#
> 
> .config looks like this:

It's pretty useless sending a mangled config.  In future, please send the
whole thing.  

The problem is that you have 

> CONFIG_CPU_FREQ_TABLE=m
> CONFIG_X86_ACPI_CPUFREQ=y

but acpi-cpufreq needs the stuff in freq_table.c.

This happens again and again and again and again.  I wish people would just
stop using `select'.  It.  Doesn't.  Work.

Either we fix select or we stop using the damn thing.


  reply	other threads:[~2006-11-08 20:06 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  9:54 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 11:11 ` 2.6.19-rc5-mm1 Reuben Farrelly
2006-11-08 20:05   ` Andrew Morton [this message]
2006-11-08 20:15     ` 2.6.19-rc5-mm1 Dave Jones
2006-11-08 20:31       ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 21:18         ` 2.6.19-rc5-mm1 Dave Jones
2006-11-09  3:09       ` [PATCH] cpufreq: select consistently (Re: 2.6.19-rc5-mm1) Randy Dunlap
2006-11-09  3:39         ` Dave Jones
2006-11-08 12:07 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 12:32   ` 2.6.19-rc5-mm1 Hesse, Christian
2006-11-08 12:54     ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 14:57       ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 18:13         ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 19:19         ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-08 20:47           ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-08 15:08 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-08 22:10   ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-08 23:31 ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09  0:17   ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09  0:44     ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09  0:55       ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09  1:04         ` 2.6.19-rc5-mm1 Rafael J. Wysocki
2006-11-09 15:42           ` 2.6.19-rc5-mm1: HPC nx6325 breakage, VESA fb problem, md-raid problem Rafael J. Wysocki
2006-11-09 17:58             ` Andrew Morton
2006-11-10  4:49               ` Andi Kleen
2006-11-10  5:15                 ` Andrew Morton
2006-11-10  6:19                   ` Andi Kleen
2006-11-10 11:21                     ` Rafael J. Wysocki
2006-11-10 11:51                       ` Andi Kleen
2006-11-10 10:44               ` Franck Bui-Huu
2006-11-10  6:28             ` Neil Brown
2006-11-10 23:20               ` Rafael J. Wysocki
2006-11-10 23:29                 ` Neil Brown
2006-11-09 15:04 ` 2.6.19-rc5-mm1 -- ppc64 ohci-hdc.c compile failure Andy Whitcroft
2006-11-09 22:43   ` Benjamin Herrenschmidt
2006-11-10  9:49     ` Paul Mackerras
2006-11-10  9:58       ` Benjamin Herrenschmidt
2006-11-09 18:43 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-09 19:04   ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-09 19:26     ` 2.6.19-rc5-mm1 Mattia Dongili
2006-11-09 21:58       ` [linux-usb-devel] 2.6.19-rc5-mm1 Alan Stern
2006-11-09 22:51         ` Andrew Morton
2006-11-09 23:39           ` Cédric Augonnet
2006-11-10  0:11             ` Andrew Morton
2006-11-10 20:17               ` Anton Vorontsov
2006-11-10 19:29           ` Benoit Boissinot
2006-11-10  3:21 ` 2.6.19-rc5-mm1 Ed Tomlinson
2006-11-10  3:31   ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-10 12:28     ` 2.6.19-rc5-mm1 Ed Tomlinson
2006-11-10 16:29 ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 16:59   ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-10 17:25     ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 20:20       ` 2.6.19-rc5-mm1 Benoit Boissinot
2006-11-10 20:41         ` 2.6.19-rc5-mm1 Thomas Gleixner
2006-11-13 15:58 ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-13 22:19   ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-13 22:26     ` 2.6.19-rc5-mm1 Mariusz Kozlowski
2006-11-13 23:37       ` 2.6.19-rc5-mm1 Andrew Morton
2006-11-13 21:03 ` [-mm patch] arch/i386/kernel/apic.c: make a function static Adrian Bunk
2006-11-14  6:54   ` Ingo Molnar
2006-11-13 21:03 ` [-mm patch] make arch/i386/kernel/io_apic.c:timer_irq_works() static again Adrian Bunk
2006-11-13 21:52   ` Zachary Amsden
2006-11-14  6:53   ` Ingo Molnar
2006-11-13 21:03 ` [-mm patch] i386: unexport read_persistent_clock Adrian Bunk
2006-11-13 21:04 ` [-mm patch] make arch/i386/kernel/cpu/common.c:alloc_gdt() static Adrian Bunk

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=20061108120547.78048229.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-linuxkernel@reub.net \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®