From: kbuild test robot <fengguang.wu@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Philipp Hachtmann <phacht@linux.vnet.ibm.com>,
Fabian Frederick <fabf@skynet.be>,
Xishi Qiu <qiuxishi@huawei.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Emil Medve <Emilian.Medve@freescale.com>
Subject: [PATCH ras] mirror: memblock_have_mirror can be static
Date: Wed, 4 Feb 2015 09:58:22 +0800 [thread overview]
Message-ID: <20150204015822.GA10853@snb> (raw)
In-Reply-To: <201502040909.te1Zvay3%fengguang.wu@intel.com>
mm/memblock.c:57:6: sparse: symbol 'memblock_have_mirror' was not declared. Should it be static?
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 911ce52..8ea1dfc 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -54,7 +54,7 @@ int memblock_debug __initdata_memblock;
#ifdef CONFIG_MOVABLE_NODE
bool movable_node_enabled __initdata_memblock = false;
#endif
-bool memblock_have_mirror __initdata_memblock = false;
+static bool memblock_have_mirror __initdata_memblock = false;
static int memblock_can_resize __initdata_memblock;
static int memblock_memory_in_slab __initdata_memblock = 0;
static int memblock_reserved_in_slab __initdata_memblock = 0;
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-02-04 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 1:58 [ras:rfc-mirror 2/2] mm/memblock.c:57:6: sparse: symbol 'memblock_have_mirror' was not declared. Should it be static? kbuild test robot
2015-02-04 1:58 ` kbuild test robot [this message]
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=20150204015822.GA10853@snb \
--to=fengguang.wu@intel.com \
--cc=Emilian.Medve@freescale.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=fabf@skynet.be \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=phacht@linux.vnet.ibm.com \
--cc=qiuxishi@huawei.com \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
/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).