public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse•de>
To: Alexey Dobriyan <adobriyan@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	linuxppc-dev@ozlabs•org
Subject: Re: next-20090216: slqb
Date: Tue, 17 Feb 2009 11:27:33 +0100	[thread overview]
Message-ID: <20090217102733.GB26402@wotan.suse.de> (raw)
In-Reply-To: <20090217005539.GA6292@x200.localdomain>

On Tue, Feb 17, 2009 at 03:55:40AM +0300, Alexey Dobriyan wrote:
> FYI, on powerpc-64-smp-n-debug-n:
> 
> mm/slqb.c: In function '__slab_free':
> mm/slqb.c:1648: error: implicit declaration of function 'slab_free_to_remote'
> mm/slqb.c: In function 'kmem_cache_open':
> mm/slqb.c:2174: error: implicit declaration of function 'kmem_cache_dyn_array_free'
> mm/slqb.c:2175: warning: label 'error_cpu_array' defined but not used
> mm/slqb.c: In function 'kmem_cache_destroy':
> mm/slqb.c:2294: error: implicit declaration of function 'claim_remote_free_list'
> mm/slqb.c: In function 'kmem_cache_reap_percpu':
> mm/slqb.c:2547: error: implicit declaration of function 'flush_remote_free_cache'
> mm/slqb.c: In function 'kmem_cache_init':
> mm/slqb.c:2783: error: 'per_cpu__kmem_cpu_nodes' undeclared (first use in this function)
> mm/slqb.c:2783: error: (Each undeclared identifier is reported only once
> mm/slqb.c:2783: error: for each function it appears in.)
> mm/slqb.c:2784: error: 'kmem_cpu_cache' undeclared (first use in this function)

Hmm, I guess this (SMP=n && NUMA=y) must be a valid config on ppc if
SLQB is the only one tripping on it, so I'll look at code to fix tihs
up.

Thanks,
Nick

  reply	other threads:[~2009-02-17 10:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  6:20 linux-next: Tree for February 16 Stephen Rothwell
2009-02-16  8:54 ` next Feb 16 build break [usb/host/fhci-*] Sachin P. Sant
     [not found]   ` <499929CB.2030004-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
2009-02-16 10:13     ` Stephen Rothwell
2009-02-16 13:40       ` [Patch - Next] [USB/FHCI] use dev_name() in place of bus_id Sachin P. Sant
     [not found]         ` <49996CBB.7040007-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
2009-02-16 13:48           ` Anton Vorontsov
2009-02-16 16:46 ` [PATCH -next] staging/phison: fix kconfig for clean build Randy Dunlap
2009-02-17  0:55 ` next-20090216: slqb Alexey Dobriyan
2009-02-17 10:27   ` Nick Piggin [this message]
2009-02-17 11:31     ` Pekka Enberg
2009-02-17 12:48       ` Peter Zijlstra
2009-02-17  9:55 ` linux-next: USB mouse won't work after resume Laurent Riffard
2009-02-17 10:35   ` Oliver Neukum
     [not found]     ` <200902171135.13329.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-02-17 13:37       ` Laurent Riffard
2009-02-17 15:12         ` Alan Stern
2009-02-17 20:42         ` Oliver Neukum
2009-02-17 21:05           ` Alan Stern
2009-02-18  9:51             ` Jiri Slaby
2009-02-18  0:31           ` Laurent Riffard
2009-02-18  8:47             ` Oliver Neukum
     [not found]           ` <200902172142.57302.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-02-18 16:51             ` Alan Stern
2009-02-18 17:06               ` Oliver Neukum

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=20090217102733.GB26402@wotan.suse.de \
    --to=npiggin@suse$(echo .)de \
    --cc=adobriyan@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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