From: Minchan Kim <minchan@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 6698/6711] <stdin>:1520:2: warning: #warning syscall process_madvise not implemented
Date: Thu, 7 May 2020 22:25:17 -0700 [thread overview]
Message-ID: <20200508052517.GA197378@google.com> (raw)
In-Reply-To: <202005080716.cUcbCQ3i%lkp@intel.com>
On Fri, May 08, 2020 at 07:37:19AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 7def1ef0f72c3ebe3e42467d2f73c4e56153fa49
> commit: db22c0ad9503eda042475aca2675cdce55249b4b [6698/6711] mm/madvise: introduce process_madvise() syscall: an external memory hinting API
> config: mips-ip27_defconfig (attached as .config)
> compiler: mips64-linux-gcc (GCC) 9.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout db22c0ad9503eda042475aca2675cdce55249b4b
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=mips
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> <stdin>:1520:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> >> <stdin>:1520:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> >> <stdin>:1520:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Thanks for the report. This patch should fix it.
From 2b93b6abc2a32683cdccb6f109617e1a597466c8 Mon Sep 17 00:00:00 2001
From: Minchan Kim <minchan@kernel.org>
Date: Thu, 7 May 2020 22:18:21 -0700
Subject: [PATCH] mm: fix build error for mips of process_madvise
kbuild test rebot reported build break of process_madvise for mips[1].
This patch should fix it.
[1] https://lore.kernel.org/linux-mm/202005080716.cUcbCQ3i%25lkp@intel.com/
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Minchan Kim <minchan@kernel.org>
---
arch/mips/kernel/syscalls/syscall_o32.tbl | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/kernel/syscalls/syscall_o32.tbl b/arch/mips/kernel/syscalls/syscall_o32.tbl
index ac586774c980..940c7f49a731 100644
--- a/arch/mips/kernel/syscalls/syscall_o32.tbl
+++ b/arch/mips/kernel/syscalls/syscall_o32.tbl
@@ -425,3 +425,4 @@
435 o32 clone3 __sys_clone3
437 o32 openat2 sys_openat2
438 o32 pidfd_getfd sys_pidfd_getfd
+439 o32 process_madvise sys_process_madvise compat_sys_process_madvise
--
2.26.2.645.ge9eca65c58-goog
prev parent reply other threads:[~2020-05-08 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 23:37 kbuild test robot
2020-05-08 5:25 ` Minchan Kim [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=20200508052517.GA197378@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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