All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	Theodore Tso <tytso@MIT.EDU>
Subject: linux-next: build failure after merge of the slab tree
Date: Mon, 31 Jan 2011 14:42:46 +1100	[thread overview]
Message-ID: <20110131144246.dfa2abe3.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

Hi all,

After merging the slab tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

fs/ext4/mballoc.c: In function 'ext4_exit_mballoc':
fs/ext4/mballoc.c:2750: error: implicit declaration of function 'kmem_cache_name'
fs/ext4/mballoc.c:2750: warning: cast to pointer from integer of different size

Caused by commit 63310467a3d1ed6a0460ec1f4268126cd1ceec2e ("mm: Remove
support for kmem_cache_name()").  Clearly the last user has not gone, yet.

I have used the version of the slab tree from next-20110121 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-01-31  3:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31  3:42 Stephen Rothwell [this message]
2011-01-31 19:32 ` linux-next: build failure after merge of the slab tree Pekka Enberg
2011-02-03 15:19   ` Christoph Lameter
2011-02-08 15:53     ` Christoph Lameter
2011-02-08 15:55       ` Christoph Lameter
2011-02-08 16:50         ` Ted Ts'o
2011-02-08 17:11         ` Sedat Dilek
2011-02-08 17:11           ` Sedat Dilek
2011-02-08 17:44           ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2024-05-01  5:28 Stephen Rothwell
2024-05-01 15:31 ` Vlastimil Babka
2022-11-25  1:49 Stephen Rothwell
2022-11-25  7:50 ` Vlastimil Babka
2022-11-24  4:39 Stephen Rothwell
2022-11-24  8:56 ` Vlastimil Babka
2022-09-06  6:51 Stephen Rothwell
2022-09-06  7:53 ` Vlastimil Babka
2022-09-06 18:37   ` Alexei Starovoitov
2022-09-07  3:05     ` Alexei Starovoitov
2022-09-07  6:40       ` Vlastimil Babka
2022-09-07  7:45       ` Stephen Rothwell
2013-07-10  2:56 Stephen Rothwell
2013-07-10  7:00 ` Pekka Enberg
2013-07-10 18:48   ` Christoph Lameter
2013-07-11  6:42     ` Pekka Enberg
2010-12-09  3:03 Stephen Rothwell
2010-12-09 16:25 ` Pekka Enberg
2010-10-27  0:33 Stephen Rothwell
2010-10-27  7:29 ` 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=20110131144246.dfa2abe3.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=tytso@MIT.EDU \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.