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>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Fabian Frederick <fabf@skynet.be>,
Philipp Hachtmann <phacht@linux.vnet.ibm.com>,
Emil Medve <Emilian.Medve@freescale.com>,
Laura Abbott <lauraa@codeaurora.org>,
Akinobu Mita <akinobu.mita@gmail.com>
Subject: [ras:rfc-mirror 2/2] mm/memblock.c:57:6: sparse: symbol 'memblock_have_mirror' was not declared. Should it be static?
Date: Wed, 4 Feb 2015 09:58:22 +0800 [thread overview]
Message-ID: <201502040909.te1Zvay3%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git rfc-mirror
head: db3eb444d5eb1bbfe26891229eff520f523f2c47
commit: db3eb444d5eb1bbfe26891229eff520f523f2c47 [2/2] mirror: allocate boot time data structures from mirrored memory
reproduce:
# apt-get install sparse
git checkout db3eb444d5eb1bbfe26891229eff520f523f2c47
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> mm/memblock.c:57:6: sparse: symbol 'memblock_have_mirror' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
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>
next 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 kbuild test robot [this message]
2015-02-04 1:58 ` [PATCH ras] mirror: memblock_have_mirror can be static kbuild test robot
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=201502040909.te1Zvay3%fengguang.wu@intel.com \
--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=lauraa@codeaurora.org \
--cc=linux-mm@kvack.org \
--cc=phacht@linux.vnet.ibm.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