From: kbuild test robot <lkp@intel.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/3] mm: Change the interface for __tlb_remove_page
Date: Sat, 4 Jun 2016 00:01:45 +0800 [thread overview]
Message-ID: <201606032349.D2Up4DnI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1464959359-7543-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Hi,
[auto build test ERROR on arm/for-next]
[also build test ERROR on v4.7-rc1 next-20160603]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Aneesh-Kumar-K-V/mm-hugetlb-Simplify-hugetlb-unmap/20160603-211611
base: http://repo.or.cz/linux-2.6/linux-2.6-arm.git for-next
config: sh-titan_defconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 5.3.1-8) 5.3.1 20160205
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
# save the attached .config to linux build tree
make.cross ARCH=sh
Note: the linux-review/Aneesh-Kumar-K-V/mm-hugetlb-Simplify-hugetlb-unmap/20160603-211611 HEAD d6ef168b95ef6261d48eff011e532d6a8798f4cd 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: 16154 bytes --]
next prev parent reply other threads:[~2016-06-03 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 13:09 [PATCH v2 1/3] mm/hugetlb: Simplify hugetlb unmap Aneesh Kumar K.V
2016-06-03 13:09 ` [PATCH v2 2/3] mm: Change the interface for __tlb_remove_page Aneesh Kumar K.V
2016-06-03 16:01 ` kbuild test robot [this message]
2016-06-03 13:09 ` [PATCH v2 3/3] mm/mmu_gather: Track page size with mmu gather and force flush if page size change Aneesh Kumar K.V
2016-06-03 13:30 ` [PATCH v2 1/3] mm/hugetlb: Simplify hugetlb unmap Aneesh Kumar K.V
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=201606032349.D2Up4DnI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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