From: kbuild test robot <lkp@intel.com>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Konstantin Khlebnikov <koct9i@gmail.com>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Jerome Marchand <jmarchan@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Dave Hansen <dave.hansen@intel.com>, Mel Gorman <mgorman@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>,
"# v4 . 3+" <stable@vger.kernel.org>
Subject: Re: [PATCH] numa: fix /proc/<pid>/numa_maps for THP
Date: Mon, 4 Apr 2016 23:56:18 +0800 [thread overview]
Message-ID: <201604042354.gHNTtjAL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459784032-15152-1-git-send-email-gerald.schaefer@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Hi Gerald,
[auto build test ERROR on v4.6-rc2]
[also build test ERROR on next-20160404]
[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/Gerald-Schaefer/numa-fix-proc-pid-numa_maps-for-THP/20160404-233625
config: tile-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=tile
All errors (new ones prefixed by >>):
fs/proc/task_mmu.c: In function 'gather_pte_stats':
>> fs/proc/task_mmu.c:1560:4: error: implicit declaration of function 'pmd_dirty'
cc1: some warnings being treated as errors
vim +/pmd_dirty +1560 fs/proc/task_mmu.c
1554 ptl = pmd_trans_huge_lock(pmd, vma);
1555 if (ptl) {
1556 struct page *page;
1557
1558 page = can_gather_numa_stats_pmd(*pmd, vma, addr);
1559 if (page)
> 1560 gather_stats(page, md, pmd_dirty(*pmd),
1561 HPAGE_PMD_SIZE/PAGE_SIZE);
1562 spin_unlock(ptl);
1563 return 0;
---
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: 43884 bytes --]
next prev parent reply other threads:[~2016-04-04 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 15:33 [PATCH] numa: fix /proc/<pid>/numa_maps for THP Gerald Schaefer
2016-04-04 15:51 ` kbuild test robot
2016-04-04 15:56 ` kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 15:24 Gerald Schaefer
2016-04-04 18:45 ` Greg KH
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=201604042354.gHNTtjAL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=jmarchan@redhat.com \
--cc=kbuild-all@01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=schwidefsky@de.ibm.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
/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