From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: mm/slab.c:3865:7: error: conflicting types for 'kmem_cache_alloc_node_trace'
Date: Tue, 25 Sep 2012 08:27:16 +0000 [thread overview]
Message-ID: <20120925082716.GA26111@localhost> (raw)
Hi Ezequiel,
FYI, kernel build failed on
4052147c0afa1cf05780ed846f37e87cdde9f628 mm, slab: Match SLAB and SLUB kmem_cache_alloc_xxx_trace() prototype
x86_64-allyesdebian
All error/warnings:
mm/slab.c:3865:7: error: conflicting types for 'kmem_cache_alloc_node_trace'
In file included from include/linux/slab.h:213:0,
from mm/slab.c:89:
include/linux/slab_def.h:162:14: note: previous declaration of 'kmem_cache_alloc_node_trace' was here
mm/slab.c: In function 'kmem_cache_alloc_node_trace':
mm/slab.c:3872:50: error: '_RET_IP' undeclared (first use in this function)
mm/slab.c:3872:50: note: each undeclared identifier is reported only once for each function it appears in
mm/slab.c: At top level:
mm/slab.c:3879:44: error: conflicting types for 'kmem_cache_alloc_node_trace'
In file included from include/linux/slab.h:213:0,
from mm/slab.c:89:
include/linux/slab_def.h:162:14: note: previous declaration of 'kmem_cache_alloc_node_trace' was here
vim +3865 mm/slab.c
3859
3860 return ret;
3861 }
3862 EXPORT_SYMBOL(kmem_cache_alloc_node);
3863
3864 #ifdef CONFIG_TRACING
> 3865 void *kmem_cache_alloc_node_trace(struct kmem_cache *cachep,
3866 gfp_t flags,
3867 int nodeid,
3868 size_t size)
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
next reply other threads:[~2012-09-25 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 8:27 Fengguang Wu [this message]
2012-09-25 10:31 ` mm/slab.c:3865:7: error: conflicting types for 'kmem_cache_alloc_node_trace' Ezequiel Garcia
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=20120925082716.GA26111@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.org \
/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.