From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Davidlohr Bueso <dave@stgolabs.net>,
David Rientjes <rientjes@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: [mmotm:master 223/507] mm/hugetlb.c:940:6: sparse: symbol 'set_page_huge_active' was not declared. Should it be static?
Date: Thu, 2 Apr 2015 09:51:14 +0800 [thread overview]
Message-ID: <201504020952.5zwySb4V%fengguang.wu@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: c226e49f30453de9c6d82b001a985254990b32e0
commit: 31e0965ee7e744862ba5d82b0e4d1dc04c947bd8 [223/507] mm-hugetlb-introduce-pagehugeactive-flag-fix
reproduce:
# apt-get install sparse
git checkout 31e0965ee7e744862ba5d82b0e4d1dc04c947bd8
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
mm/hugetlb.c:933:6: sparse: symbol 'page_huge_active' was not declared. Should it be static?
>> mm/hugetlb.c:940:6: sparse: symbol 'set_page_huge_active' was not declared. Should it be static?
>> mm/hugetlb.c:946:6: sparse: symbol 'clear_page_huge_active' was not declared. Should it be static?
mm/hugetlb.c:2071:20: sparse: symbol 'node_hstates' was not declared. Should it be static?
mm/hugetlb.c:1327:20: sparse: context imbalance in 'gather_surplus_pages' - unexpected unlock
mm/hugetlb.c:2950:9: sparse: context imbalance in 'hugetlb_cow' - unexpected unlock
mm/hugetlb.c:3442:25: sparse: context imbalance in 'follow_hugetlb_page' - different lock contexts for basic block
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-04-02 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 1:51 kbuild test robot [this message]
2015-04-02 1:51 ` [PATCH mmotm] set_page_huge_active() 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=201504020952.5zwySb4V%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=lcapitulino@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.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