From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Mel Gorman <mgorman@suse.de>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mel:mm-vmscan-node-lru-follow-up-v2r1 107/363] mm/memory.c:1210:4: error: implicit declaration of function '__tlb_adjust_range'
Date: Sat, 16 Jul 2016 01:53:20 +0800 [thread overview]
Message-ID: <201607160118.LFCO6SgR%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git mm-vmscan-node-lru-follow-up-v2r1
head: d5502746ab169a810a4adc0ec760117790e477df
commit: 516dfd6c8353f33af29b54a4251f9130cd8b78ca [107/363] mm: change the interface for __tlb_remove_page()
config: ia64-generic_defconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 4.9.0
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 516dfd6c8353f33af29b54a4251f9130cd8b78ca
# save the attached .config to linux build tree
make.cross ARCH=ia64
Note: the mel/mm-vmscan-node-lru-follow-up-v2r1 HEAD d5502746ab169a810a4adc0ec760117790e477df builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
mm/memory.c: In function 'zap_pte_range':
>> mm/memory.c:1210:4: error: implicit declaration of function '__tlb_adjust_range' [-Werror=implicit-function-declaration]
__tlb_adjust_range(tlb, tlb->addr);
^
>> mm/memory.c:1210:31: error: 'struct mmu_gather' has no member named 'addr'
__tlb_adjust_range(tlb, tlb->addr);
^
cc1: some warnings being treated as errors
vim +/__tlb_adjust_range +1210 mm/memory.c
1204 */
1205 if (force_flush) {
1206 force_flush = 0;
1207 tlb_flush_mmu_free(tlb);
1208 if (pending_page) {
1209 /* remove the page with new size */
> 1210 __tlb_adjust_range(tlb, tlb->addr);
1211 __tlb_remove_page(tlb, pending_page);
1212 pending_page = NULL;
1213 }
---
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: 18257 bytes --]
reply other threads:[~2016-07-15 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201607160118.LFCO6SgR%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--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