All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>, Ralf Baechle <ralf@linux-mips.org>,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [mmotm:master 174/397] mm/madvise.c:42:7: error: 'MADV_FREE' undeclared
Date: Thu, 27 Nov 2014 10:18:19 +0900	[thread overview]
Message-ID: <20141127011819.GA21891@bbox> (raw)
In-Reply-To: <201411270835.hrrJeFPX%fengguang.wu@intel.com>

On Thu, Nov 27, 2014 at 08:18:37AM +0800, kbuild test robot wrote:
> tree:   git://git.cmpxchg.org/linux-mmotm.git master
> head:   a2d887dee78e23dc092ff14ae2ad22592437a328
> commit: 7eba9427dd923bdf1cc5f88bb0fb880fe1268be0 [174/397] mm: support madvise(MADV_FREE)
> config: xtensa-common_defconfig (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
>   git checkout 7eba9427dd923bdf1cc5f88bb0fb880fe1268be0
>   # save the attached .config to linux build tree
>   make.cross ARCH=xtensa 
> 
> All error/warnings:
> 
>    mm/madvise.c: In function 'madvise_need_mmap_write':
> >> mm/madvise.c:42:7: error: 'MADV_FREE' undeclared (first use in this function)
>      case MADV_FREE:
>           ^
>    mm/madvise.c:42:7: note: each undeclared identifier is reported only once for each function it appears in
>    mm/madvise.c: In function 'madvise_vma':
> >> mm/madvise.c:515:7: error: 'MADV_FREE' undeclared (first use in this function)
>      case MADV_FREE:
>           ^
>    mm/madvise.c: In function 'madvise_behavior_valid':
> >> mm/madvise.c:542:7: error: 'MADV_FREE' undeclared (first use in this function)
>      case MADV_FREE:
>           ^
> 
> vim +/MADV_FREE +42 mm/madvise.c
> 
>     36	static int madvise_need_mmap_write(int behavior)
>     37	{
>     38		switch (behavior) {
>     39		case MADV_REMOVE:
>     40		case MADV_WILLNEED:
>     41		case MADV_DONTNEED:
>   > 42		case MADV_FREE:
>     43			return 0;
>     44		default:
>     45			/* be safe, default to 1. list exceptions explicitly */
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

Thanks.

Below should fix the problem.

  reply	other threads:[~2014-11-27  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  0:18 [mmotm:master 174/397] mm/madvise.c:42:7: error: 'MADV_FREE' undeclared kbuild test robot
2014-11-27  1:18 ` Minchan Kim [this message]
2014-11-27  8:08   ` Max Filippov

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=20141127011819.GA21891@bbox \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris@zankel.net \
    --cc=deller@gmx.de \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jcmvbkbc@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=mtk.manpages@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.