From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 190/376] mm/page_alloc.c:995: warning: 'free_pages_prepare' declared inline after being called
Date: Thu, 28 Apr 2016 12:22:04 +0800 [thread overview]
Message-ID: <201604281203.VLTNjuRT%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 3eb62ac3b0fd7cf3656c0e2a4ed3b0833bb2e952
commit: 2eb5dfe5f118fae2f81ddb971edb5280e1ce3e5e [190/376] mm-page_alloc-dont-duplicate-code-in-free_pcp_prepare-fix
config: avr32-atngw100_defconfig (attached as .config)
compiler:
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 2eb5dfe5f118fae2f81ddb971edb5280e1ce3e5e
# save the attached .config to linux build tree
make.cross ARCH=avr32
All warnings (new ones prefixed by >>):
>> mm/page_alloc.c:995: warning: 'free_pages_prepare' declared inline after being called
mm/page_alloc.c:995: warning: previous declaration of 'free_pages_prepare' was here
vim +/free_pages_prepare +995 mm/page_alloc.c
979 if (unlikely(!PageTail(page))) {
980 bad_page(page, "PageTail not set", 0);
981 goto out;
982 }
983 if (unlikely(compound_head(page) != head_page)) {
984 bad_page(page, "compound_head not consistent", 0);
985 goto out;
986 }
987 ret = 0;
988 out:
989 page->mapping = NULL;
990 clear_compound_head(page);
991 return ret;
992 }
993
994 static bool free_pages_prepare(struct page *page, unsigned int order,
> 995 bool check_free);
996
997 #ifdef CONFIG_DEBUG_VM
998 static inline bool free_pcp_prepare(struct page *page)
999 {
1000 return free_pages_prepare(page, 0, true);
1001 }
1002
1003 static inline bool bulkfree_pcp_prepare(struct page *page)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 12366 bytes --]
next reply other threads:[~2016-04-28 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 4:22 kbuild test robot [this message]
2016-04-28 21:20 ` Andrew Morton
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=201604281203.VLTNjuRT%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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