From: kbuild test robot <lkp@intel.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, n-horiguchi@ah.jp.nec.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] mm/madvise: Move up the behavior parameter validation
Date: Thu, 13 Apr 2017 21:59:13 +0800 [thread overview]
Message-ID: <201704132103.LUYgcBS2%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170413092008.5437-1-khandual@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
Hi Anshuman,
[auto build test ERROR on next-20170412]
[also build test ERROR on v4.11-rc6]
[cannot apply to mmotm/master v4.9-rc8 v4.9-rc7 v4.9-rc6]
[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/Anshuman-Khandual/mm-madvise-Move-up-the-behavior-parameter-validation/20170413-203541
config: parisc-c3000_defconfig (attached as .config)
compiler: hppa-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=parisc
All errors (new ones prefixed by >>):
mm/madvise.c: In function 'madvise_behavior_valid':
>> mm/madvise.c:690:7: error: 'MADV_SOFT_OFFLINE' undeclared (first use in this function)
case MADV_SOFT_OFFLINE:
^~~~~~~~~~~~~~~~~
mm/madvise.c:690:7: note: each undeclared identifier is reported only once for each function it appears in
>> mm/madvise.c:691:7: error: 'MADV_HWPOISON' undeclared (first use in this function)
case MADV_HWPOISON:
^~~~~~~~~~~~~
vim +/MADV_SOFT_OFFLINE +690 mm/madvise.c
684 #ifdef CONFIG_TRANSPARENT_HUGEPAGE
685 case MADV_HUGEPAGE:
686 case MADV_NOHUGEPAGE:
687 #endif
688 case MADV_DONTDUMP:
689 case MADV_DODUMP:
> 690 case MADV_SOFT_OFFLINE:
> 691 case MADV_HWPOISON:
692 return true;
693
694 default:
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 14651 bytes --]
next prev parent reply other threads:[~2017-04-13 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 9:20 Anshuman Khandual
2017-04-13 13:59 ` kbuild test robot [this message]
2017-04-14 13:51 ` [PATCH V2] " Anshuman Khandual
2017-04-17 5:27 ` Naoya Horiguchi
2017-04-18 2:46 ` Anshuman Khandual
2017-04-18 5:28 ` [PATCH V3] " Anshuman Khandual
2017-04-18 21:01 ` David Rientjes
2017-04-19 0:46 ` Naoya Horiguchi
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=201704132103.LUYgcBS2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
/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