From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Pekka Enberg <penberg@cs•helsinki.fi>,
Christoph Lameter <cl@linux-foundation•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: slab tree build failure
Date: Mon, 7 Dec 2009 15:11:36 +1100 [thread overview]
Message-ID: <20091207151136.46c85ee4.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
Hi all,
Today's linux-next build (x86_64 allmodconfig) failed like this:
tests/slab_test.c: In function 'test_func':
tests/slab_test.c:176: error: implicit declaration of function 'set_cpus_allowed'
Caused by commit 1c999557258d251e2e5790de4b723d5996c06d5d ("Add slab
performance tests").
set_cpus_allowed it now only defined if CONFIG_CPUMASK_OFFSTACK is not
set. This was changed by commit e0ad955680878998ff7dc51ce06ddad12260423a
("cpumask: don't define set_cpus_allowed() if CONFIG_CPUMASK_OFFSTACK=y")
which entered Linus' tree before 2.6.32-rc1.
I have used the version of the slab tree from next-20091204 for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-12-07 4:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 4:11 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-08 3:44 linux-next: slab tree build failure Stephen Rothwell
2009-09-07 5:37 Stephen Rothwell
2009-09-07 6:10 ` Pekka Enberg
2009-09-07 7:31 ` Stephen Rothwell
2009-09-07 7:43 ` Pekka Enberg
2009-09-07 8:29 ` Stephen Rothwell
2009-09-07 9:04 ` Heiko Carstens
2009-09-07 9:22 ` Pekka Enberg
2009-09-07 8:35 ` Catalin Marinas
2009-09-08 16:32 ` Luis R. Rodriguez
2009-06-19 4:16 Stephen Rothwell
2009-06-19 10:40 ` Benjamin Herrenschmidt
2009-06-22 9:09 ` Pekka Enberg
2008-11-03 4:42 Stephen Rothwell
2008-11-03 5:14 ` Dave Chinner
2008-11-03 9:38 ` Pekka Enberg
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=20091207151136.46c85ee4.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=cl@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=penberg@cs$(echo .)helsinki.fi \
/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