All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [glommer-memcg:slab-common/slabinfo 17/21] mm/slab.c:4415:9: error: conflicting types for 'slabinfo_
Date: Thu, 27 Sep 2012 17:48:31 +0000	[thread overview]
Message-ID: <20120927174831.GA5517@localhost> (raw)

Hi Glauber,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/glommer/memcg.git slab-common/slabinfo
head:   0521160acc51bc8385807752e69dd38d976aef22
commit: 514d13cfa0bed7c434b594d4f989df63c8ca6ba6 [17/21] move slabinfo processing to slab_common.c
config: blackfin-BF533-EZKIT_defconfig

All error/warnings:

In file included from mm/slab.c:90:0:
mm/slab.h:50:35: warning: 'struct seq_file' declared inside parameter list [enabled by default]
mm/slab.h:50:35: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
mm/slab.h:52:26: warning: 'struct seq_file' declared inside parameter list [enabled by default]
mm/slab.h:55:10: warning: 'struct file' declared inside parameter list [enabled by default]
mm/slab.c:4287:6: error: conflicting types for 'print_slabinfo_header'
In file included from mm/slab.c:90:0:
mm/slab.h:50:6: note: previous declaration of 'print_slabinfo_header' was here
mm/slab.c:4310:5: error: conflicting types for 'slabinfo_show'
In file included from mm/slab.c:90:0:
mm/slab.h:52:5: note: previous declaration of 'slabinfo_show' was here
mm/slab.c:4415:9: error: conflicting types for 'slabinfo_write'
In file included from mm/slab.c:90:0:
mm/slab.h:54:9: note: previous declaration of 'slabinfo_write' was here

vim +4415 mm/slab.c

^1da177e (Linus Torvalds 2005-04-16  4409)  * slabinfo_write - Tuning for the slab allocator
^1da177e (Linus Torvalds 2005-04-16  4410)  * @file: unused
^1da177e (Linus Torvalds 2005-04-16  4411)  * @buffer: user buffer
^1da177e (Linus Torvalds 2005-04-16  4412)  * @count: data length
^1da177e (Linus Torvalds 2005-04-16  4413)  * @ppos: unused
^1da177e (Linus Torvalds 2005-04-16  4414)  */
514d13cf (Glauber Costa  2012-09-26 @4415) ssize_t slabinfo_write(struct file *file, const char __user *buffer,
b28a02de (Pekka Enberg   2006-01-08  4416) 		       size_t count, loff_t *ppos)
^1da177e (Linus Torvalds 2005-04-16  4417) {
b28a02de (Pekka Enberg   2006-01-08  4418) 	char kbuf[MAX_SLABINFO_WRITE + 1], *tmp;

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

                 reply	other threads:[~2012-09-27 17:48 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=20120927174831.GA5517@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.