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:kmemcg-slab 26/33] drivers/firmware/memmap.c:240:19: error: conflicting types for 'me
Date: Mon, 15 Oct 2012 02:42:30 +0000	[thread overview]
Message-ID: <20121015024230.GA16122@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: d17ddfd35a7329643b2fb442ade58e2974a2a05c [26/33] sl[au]b: Allocate objects from memcg cache
config: ia64-allmodconfig # make ARCH=ia64 allmodconfig
branch date: 3 hours ago
commit date: 4 hours ago

All error/warnings:

drivers/firmware/memmap.c:240:19: error: conflicting types for 'memmap_init'
arch/ia64/include/asm/pgtable.h:565:17: note: previous declaration of 'memmap_init' was here

vim +240 drivers/firmware/memmap.c

69ac9cd6 Bernhard Walle            2008-06-27  232  /*
69ac9cd6 Bernhard Walle            2008-06-27  233   * Initialises stuff and adds the entries in the map_entries list to
69ac9cd6 Bernhard Walle            2008-06-27  234   * sysfs. Important is that firmware_map_add() and firmware_map_add_early()
31bad924 Bernhard Walle            2008-08-12  235   * must be called before late_initcall. That's just because that function
31bad924 Bernhard Walle            2008-08-12  236   * is called as late_initcall() function, which means that if you call
31bad924 Bernhard Walle            2008-08-12  237   * firmware_map_add() or firmware_map_add_early() afterwards, the entries
31bad924 Bernhard Walle            2008-08-12  238   * are not added to sysfs.
69ac9cd6 Bernhard Walle            2008-06-27  239   */
69ac9cd6 Bernhard Walle            2008-06-27 @240  static int __init memmap_init(void)
69ac9cd6 Bernhard Walle            2008-06-27  241  {
69ac9cd6 Bernhard Walle            2008-06-27  242  	struct firmware_map_entry *entry;
69ac9cd6 Bernhard Walle            2008-06-27  243  
d96ae530 akpm@linux-foundation.org 2010-03-05  244  	list_for_each_entry(entry, &map_entries, list)
d96ae530 akpm@linux-foundation.org 2010-03-05  245  		add_sysfs_fw_map_entry(entry);
69ac9cd6 Bernhard Walle            2008-06-27  246  
69ac9cd6 Bernhard Walle            2008-06-27  247  	return 0;
69ac9cd6 Bernhard Walle            2008-06-27  248  }

The code at line 240 was first introduced by commit:
69ac9cd sysfs: add /sys/firmware/memmap


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

             reply	other threads:[~2012-10-15  2:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  2:42 Fengguang Wu [this message]
2012-10-15  8:39 ` [glommer-memcg:kmemcg-slab 26/33] drivers/firmware/memmap.c:240:19: error: conflicting types for Glauber Costa
2012-10-15 11:17 ` Fengguang Wu

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=20121015024230.GA16122@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.