[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49ED0869.5090507@oracle.com>
Date: Mon, 20 Apr 2009 16:42:33 -0700
From: Randy Dunlap <randy.dunlap_ocs10g@...cle.com>
To: "Luck, Tony" <tony.luck@...el.com>
CC: Nick Piggin <npiggin@...e.de>,
Pekka Enberg <penberg@...helsinki.fi>,
linux-kernel@...r.kernel.org
Subject: Re: linux-next ia64 build problems in slqb
Luck, Tony wrote:
> The ia64 "allnoconfig" build ends up with the (possibly dubious) combination
> of .config options:
>
> CONFIG_SMP=n
> CONFIG_NUMA=y
>
> which leads to the following build problems with mm/slqb.c
>
> CC mm/slqb.o
> mm/slqb.c: In function ‘__slab_free’:
> mm/slqb.c:1735: error: implicit declaration of function ‘slab_free_to_remote’
> mm/slqb.c: In function ‘kmem_cache_open’:
> mm/slqb.c:2274: error: implicit declaration of function ‘kmem_cache_dyn_array_free’
> mm/slqb.c:2275: warning: label ‘error_cpu_array’ defined but not used
> mm/slqb.c: In function ‘kmem_cache_destroy’:
> mm/slqb.c:2395: error: implicit declaration of function ‘claim_remote_free_list’
> mm/slqb.c: In function ‘kmem_cache_init’:
> mm/slqb.c:2885: error: ‘per_cpu__kmem_cpu_nodes’ undeclared (first use in this function)
> mm/slqb.c:2885: error: (Each undeclared identifier is reported only once
> mm/slqb.c:2885: error: for each function it appears in.)
> mm/slqb.c:2886: error: ‘kmem_cpu_cache’ undeclared (first use in this function)
Does this patch fix it?
http://lkml.org/lkml/2009/4/20/30
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists