From: Minchan Kim <minchan@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 5810/5816] <stdin>:1529:2: warning: #warning syscall process_madvise not implemented
Date: Wed, 09 Sep 2020 10:36:55 -0700 [thread overview]
Message-ID: <20200909173655.GC2435453@google.com> (raw)
In-Reply-To: <202009091457.VbvdJgdg%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4424 bytes --]
On Wed, Sep 09, 2020 at 02:05:01PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: dff9f829e5b0181d4ed9d35aa62d695292399b54
> commit: 6d0ecd769ce298f6f20e2161f48eb1e1f7b32434 [5810/5816] mm/madvise: introduce process_madvise() syscall: an external memory hinting API
> config: mips-ip28_defconfig (attached as .config)
> compiler: mips64-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 6d0ecd769ce298f6f20e2161f48eb1e1f7b32434
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> <stdin>:1529:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> >> <stdin>:1529:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> arch/mips/kernel/asm-offsets.c:26:6: warning: no previous prototype for 'output_ptreg_defines' [-Wmissing-prototypes]
> 26 | void output_ptreg_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:78:6: warning: no previous prototype for 'output_task_defines' [-Wmissing-prototypes]
> 78 | void output_task_defines(void)
> | ^~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:93:6: warning: no previous prototype for 'output_thread_info_defines' [-Wmissing-prototypes]
> 93 | void output_thread_info_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:110:6: warning: no previous prototype for 'output_thread_defines' [-Wmissing-prototypes]
> 110 | void output_thread_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:138:6: warning: no previous prototype for 'output_thread_fpu_defines' [-Wmissing-prototypes]
> 138 | void output_thread_fpu_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:181:6: warning: no previous prototype for 'output_mm_defines' [-Wmissing-prototypes]
> 181 | void output_mm_defines(void)
> | ^~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:242:6: warning: no previous prototype for 'output_sc_defines' [-Wmissing-prototypes]
> 242 | void output_sc_defines(void)
> | ^~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:255:6: warning: no previous prototype for 'output_signal_defined' [-Wmissing-prototypes]
> 255 | void output_signal_defined(void)
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:348:6: warning: no previous prototype for 'output_kvm_defines' [-Wmissing-prototypes]
> 348 | void output_kvm_defines(void)
> | ^~~~~~~~~~~~~~~~~~
> >> <stdin>:1529: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(a)lists.01.org
Andrew, please pick this up.
Thanks.
>From ae41bb036c55fadff102082755ba6d645e0db3e1 Mon Sep 17 00:00:00 2001
From: Minchan Kim <minchan@kernel.org>
Date: Wed, 9 Sep 2020 10:30:49 -0700
Subject: [PATCH]
mm-madvise-introduce-process_madvise-syscall-an-external-memory-hinting-api-fix-fix-fix
fix mips build
warning: #warning syscall process_madvise not implemented [-Wcpp]
warning: #warning syscall process_madvise not implemented [-Wcpp]
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Minchan Kim <minchan@kernel.org>
---
arch/mips/kernel/syscalls/syscall_n64.tbl | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/kernel/syscalls/syscall_n64.tbl b/arch/mips/kernel/syscalls/syscall_n64.tbl
index 97969b679f80..0a55d89056b1 100644
--- a/arch/mips/kernel/syscalls/syscall_n64.tbl
+++ b/arch/mips/kernel/syscalls/syscall_n64.tbl
@@ -355,3 +355,4 @@
438 n64 pidfd_getfd sys_pidfd_getfd
439 n64 faccessat2 sys_faccessat2
440 n64 watch_mount sys_watch_mount
+441 n64 process_madvise sys_process_madvise
--
2.28.0.526.ge36021eeef-goog
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: kernel test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
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 5810/5816] <stdin>:1529:2: warning: #warning syscall process_madvise not implemented
Date: Wed, 9 Sep 2020 10:36:55 -0700 [thread overview]
Message-ID: <20200909173655.GC2435453@google.com> (raw)
In-Reply-To: <202009091457.VbvdJgdg%lkp@intel.com>
On Wed, Sep 09, 2020 at 02:05:01PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: dff9f829e5b0181d4ed9d35aa62d695292399b54
> commit: 6d0ecd769ce298f6f20e2161f48eb1e1f7b32434 [5810/5816] mm/madvise: introduce process_madvise() syscall: an external memory hinting API
> config: mips-ip28_defconfig (attached as .config)
> compiler: mips64-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 6d0ecd769ce298f6f20e2161f48eb1e1f7b32434
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> <stdin>:1529:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> >> <stdin>:1529:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> --
> arch/mips/kernel/asm-offsets.c:26:6: warning: no previous prototype for 'output_ptreg_defines' [-Wmissing-prototypes]
> 26 | void output_ptreg_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:78:6: warning: no previous prototype for 'output_task_defines' [-Wmissing-prototypes]
> 78 | void output_task_defines(void)
> | ^~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:93:6: warning: no previous prototype for 'output_thread_info_defines' [-Wmissing-prototypes]
> 93 | void output_thread_info_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:110:6: warning: no previous prototype for 'output_thread_defines' [-Wmissing-prototypes]
> 110 | void output_thread_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:138:6: warning: no previous prototype for 'output_thread_fpu_defines' [-Wmissing-prototypes]
> 138 | void output_thread_fpu_defines(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:181:6: warning: no previous prototype for 'output_mm_defines' [-Wmissing-prototypes]
> 181 | void output_mm_defines(void)
> | ^~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:242:6: warning: no previous prototype for 'output_sc_defines' [-Wmissing-prototypes]
> 242 | void output_sc_defines(void)
> | ^~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:255:6: warning: no previous prototype for 'output_signal_defined' [-Wmissing-prototypes]
> 255 | void output_signal_defined(void)
> | ^~~~~~~~~~~~~~~~~~~~~
> arch/mips/kernel/asm-offsets.c:348:6: warning: no previous prototype for 'output_kvm_defines' [-Wmissing-prototypes]
> 348 | void output_kvm_defines(void)
> | ^~~~~~~~~~~~~~~~~~
> >> <stdin>:1529: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
Andrew, please pick this up.
Thanks.
From ae41bb036c55fadff102082755ba6d645e0db3e1 Mon Sep 17 00:00:00 2001
From: Minchan Kim <minchan@kernel.org>
Date: Wed, 9 Sep 2020 10:30:49 -0700
Subject: [PATCH]
mm-madvise-introduce-process_madvise-syscall-an-external-memory-hinting-api-fix-fix-fix
fix mips build
warning: #warning syscall process_madvise not implemented [-Wcpp]
warning: #warning syscall process_madvise not implemented [-Wcpp]
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Minchan Kim <minchan@kernel.org>
---
arch/mips/kernel/syscalls/syscall_n64.tbl | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/kernel/syscalls/syscall_n64.tbl b/arch/mips/kernel/syscalls/syscall_n64.tbl
index 97969b679f80..0a55d89056b1 100644
--- a/arch/mips/kernel/syscalls/syscall_n64.tbl
+++ b/arch/mips/kernel/syscalls/syscall_n64.tbl
@@ -355,3 +355,4 @@
438 n64 pidfd_getfd sys_pidfd_getfd
439 n64 faccessat2 sys_faccessat2
440 n64 watch_mount sys_watch_mount
+441 n64 process_madvise sys_process_madvise
--
2.28.0.526.ge36021eeef-goog
next prev parent reply other threads:[~2020-09-09 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 6:05 [linux-next:master 5810/5816] <stdin>:1529:2: warning: #warning syscall process_madvise not implemented kernel test robot
2020-09-09 6:05 ` kernel test robot
2020-09-09 17:36 ` Minchan Kim [this message]
2020-09-09 17:36 ` Minchan Kim
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=20200909173655.GC2435453@google.com \
--to=minchan@kernel.org \
--cc=kbuild-all@lists.01.org \
/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.