From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Minchan Kim <minchan@kernel.org>,
kbuild-all@lists.01.org, Johannes Weiner <hannes@cmpxchg.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [hnaz-linux-mm:master 196/224] arch/arm64/include/asm/unistd32.h:897:11: error: '__NR_process_madvise' undeclared here (not in a function)
Date: Thu, 25 Jun 2020 12:31:56 -0700 [thread overview]
Message-ID: <20200625123156.3b376d0e55df9918365b7fd9@linux-foundation.org> (raw)
In-Reply-To: <202006252105.MjJjDcon%lkp@intel.com>
On Thu, 25 Jun 2020 21:53:09 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://github.com/hnaz/linux-mm master
> head: 40d47c26669bdbaa1062e636371a4bf4f9b6f0e5
> commit: 25003a4287763edd30991a6b03e15d1c8d434565 [196/224] mm/madvise: introduce process_madvise() syscall: an external memory hinting API
> config: arm64-allyesconfig (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 25003a4287763edd30991a6b03e15d1c8d434565
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All error/warnings (new ones prefixed by >>):
>
> In file included from arch/arm64/kernel/sys32.c:127:
> >> arch/arm64/include/asm/unistd32.h:896: warning: "__NR_fsinfo" redefined
oops, thanks.
--- a/arch/arm64/include/asm/unistd32.h~mm-madvise-introduce-process_madvise-syscall-an-external-memory-hinting-api-fix
+++ a/arch/arm64/include/asm/unistd32.h
@@ -893,7 +893,7 @@ __SYSCALL(__NR_watch_mount, sys_watch_mo
__SYSCALL(__NR_watch_sb, sys_watch_sb)
#define __NR_fsinfo 442
__SYSCALL(__NR_fsinfo, sys_fsinfo)
-#define __NR_fsinfo 443
+#define __NR_process_madvise 443
__SYSCALL(__NR_process_madvise, compat_sys_process_madvise)
/*
_
prev parent reply other threads:[~2020-06-25 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:53 kernel test robot
2020-06-25 19:31 ` Andrew Morton [this message]
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=20200625123156.3b376d0e55df9918365b7fd9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=minchan@kernel.org \
--cc=surenb@google.com \
--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