From: kbuild test robot <lkp@intel.com>
To: Yang Shi <yang.shi@linaro.org>
Cc: kbuild-all@01.org, akpm@linux-foundation.org,
kirill.shutemov@linux.intel.com, aarcange@redhat.com,
hughd@google.com, mgorman@suse.de, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] mm: move huge_pmd_set_accessed out of huge_memory.c
Date: Thu, 21 Apr 2016 03:04:40 +0800 [thread overview]
Message-ID: <201604210302.gvs4r2dP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1461176698-9714-1-git-send-email-yang.shi@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Hi,
[auto build test ERROR on v4.6-rc4]
[also build test ERROR on next-20160420]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Yang-Shi/mm-move-huge_pmd_set_accessed-out-of-huge_memory-c/20160421-025318
config: mips-allyesconfig (attached as .config)
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=mips
All errors (new ones prefixed by >>):
mm/memory.c: In function 'huge_pmd_set_accessed':
>> mm/memory.c:3304:10: error: implicit declaration of function 'pmd_mkyoung' [-Werror=implicit-function-declaration]
entry = pmd_mkyoung(orig_pmd);
^
>> mm/memory.c:3304:8: error: incompatible types when assigning to type 'pmd_t {aka struct <anonymous>}' from type 'int'
entry = pmd_mkyoung(orig_pmd);
^
cc1: some warnings being treated as errors
vim +/pmd_mkyoung +3304 mm/memory.c
3298 unsigned long haddr;
3299
3300 ptl = pmd_lock(mm, pmd);
3301 if (unlikely(!pmd_same(*pmd, orig_pmd)))
3302 goto unlock;
3303
> 3304 entry = pmd_mkyoung(orig_pmd);
3305 haddr = address & HPAGE_PMD_MASK;
3306 if (pmdp_set_access_flags(vma, haddr, pmd, entry, dirty))
3307 update_mmu_cache_pmd(vma, address, pmd);
---
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: 41426 bytes --]
next prev parent reply other threads:[~2016-04-20 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 18:24 Yang Shi
2016-04-20 19:04 ` kbuild test robot [this message]
2016-04-20 19:09 ` kbuild test robot
2016-04-20 19:20 ` kbuild test robot
2016-04-20 21:00 ` Shi, Yang
2016-04-21 7:30 ` Kirill A. Shutemov
2016-04-21 22:56 ` Shi, Yang
2016-04-22 9:48 ` Kirill A. Shutemov
2016-04-29 18:09 ` Shi, Yang
2016-04-21 9:15 ` Hugh Dickins
2016-04-21 22:57 ` Shi, Yang
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=201604210302.gvs4r2dP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=yang.shi@linaro.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