From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [glommer-memcg:kmemcg-slab 30/33] mm/slab_common.c:250:6: error: conflicting types for 'print_slabin
Date: Fri, 12 Oct 2012 16:55:22 +0000 [thread overview]
Message-ID: <20121012165522.GA20312@localhost> (raw)
Hi Glauber,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/glommer/memcg.git kmemcg-slab
head: f7dc2a43ce771e73443c82eb25d95f72f8161b45
commit: 0f901d86f02ebf93cd584f9f09b4b6f4add9caa8 [30/33] Aggregate memcg cache values in slabinfo
config: cris-allyesconfig # make ARCH=cris
All error/warnings:
In file included from kernel/fork.c:14:0:
include/linux/slab.h:224:45: warning: 'struct seq_file' declared inside parameter list [enabled by default]
include/linux/slab.h:224:45: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
include/linux/slab.h:225:35: warning: 'struct seq_file' declared inside parameter list [enabled by default]
--
In file included from mm/slab_common.c:6:0:
include/linux/slab.h:224:45: warning: 'struct seq_file' declared inside parameter list [enabled by default]
include/linux/slab.h:224:45: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
include/linux/slab.h:225:35: warning: 'struct seq_file' declared inside parameter list [enabled by default]
mm/slab_common.c:250:6: error: conflicting types for 'print_slabinfo_header'
include/linux/slab.h:225:6: note: previous declaration of 'print_slabinfo_header' was here
mm/slab_common.c:320:5: error: conflicting types for 'cache_show'
include/linux/slab.h:224:5: note: previous declaration of 'cache_show' was here
--
In file included from mm/bootmem.c:13:0:
include/linux/slab.h:224:45: warning: 'struct seq_file' declared inside parameter list [enabled by default]
include/linux/slab.h:224:45: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
include/linux/slab.h:225:35: warning: 'struct seq_file' declared inside parameter list [enabled by default]
mm/bootmem.c: In function 'mark_bootmem':
mm/bootmem.c:361:1: warning: control reaches end of non-void function [-Wreturn-type]
vim +250 mm/slab_common.c
97d06609 Christoph Lameter 2012-07-06 244 int slab_is_available(void)
97d06609 Christoph Lameter 2012-07-06 245 {
97d06609 Christoph Lameter 2012-07-06 246 return slab_state >= UP;
97d06609 Christoph Lameter 2012-07-06 247 }
4d93335e Glauber Costa 2012-09-26 248
4d93335e Glauber Costa 2012-09-26 249 #ifdef CONFIG_SLABINFO
0f901d86 Glauber Costa 2012-10-01 @250 void print_slabinfo_header(struct seq_file *m)
5c939166 Glauber Costa 2012-09-26 251 {
5c939166 Glauber Costa 2012-09-26 252 /*
5c939166 Glauber Costa 2012-09-26 253 * Output format version, so at least we can change it
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-12 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121012165522.GA20312@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).