On Tue, 7 Nov 2006 22:52:59 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:

> On Wed, 8 Nov 2006 15:01:41 +0900
> KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> 
> > 
> > While compiling 2.6.19-rc4-mm2 on ia64, I met this compile error.
> > ==
> >   CC [M]  drivers/acpi/processor_idle.o
> > drivers/acpi/processor_idle.c:43:22: asm/apic.h: No such file or directory
> > drivers/acpi/processor_idle.c: In function `acpi_processor_power_seq_show':
> > drivers/acpi/processor_idle.c:1202: warning: long long unsigned int format, 
> > u64 arg (arg 5)
> > ==
> > 
> > This is because of acpi-include-apic-h.patch, maybe.
> > ia64 doesn't have asm/acpi.h
> 
> That got fixed (by ugly means).

Ah, okay. I'll move to rc5-mm1. Thank you.

> 
> > my .config is attached.
> 
> But rc5-mm1 remains broken with that .config:
> 
> arch/ia64/pci/pci.c: In function `pci_acpi_scan_root':
> arch/ia64/pci/pci.c:354: warning: implicit declaration of function 
> `pxm_to_node'
> ...
> arch/ia64/pci/built-in.o(.text+0xe92): In function `pci_acpi_scan_root':
> : undefined reference to `pxm_to_node'
> 
> This bug exists in mainline.
> 

How about this ? Maybe ia64 people's review is necessary.

-Kame
==
When ACPI && NUMA, pxm_to_node is used and it exists in drivers/acpi/numa.c

Signed-Off-By: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>

Index: linux-2.6.19-rc4-mm2/arch/ia64/Kconfig
===================================================================
--- linux-2.6.19-rc4-mm2.orig/arch/ia64/Kconfig 2006-11-08 14:15:21.000000000 
+0900
+++ linux-2.6.19-rc4-mm2/arch/ia64/Kconfig      2006-11-08 16:16:40.000000000 
+0900
@@ -353,6 +353,7 @@
        bool "NUMA support"
        depends on !IA64_HP_SIM && !FLATMEM
        default y if IA64_SGI_SN2
+       select ACPI_NUMA if ACPI
        help
          Say Y to compile the kernel to support NUMA (Non-Uniform Memory
          Access).  This option is for configuring high-end multiprocessor

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to