From: kbuild test robot <lkp@intel.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
criu@openvz.org, Arnd Bergmann <arnd@arndb.de>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Triplett <josh@joshtriplett.org>,
Jann Horn <jannh@google.com>,
Greg KH <gregkh@linuxfoundation.org>,
Andrei Vagin <avagin@openvz.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 3/4] x86: wire up the process_vmsplice syscall
Date: Tue, 28 Nov 2017 20:35:12 +0800 [thread overview]
Message-ID: <201711282047.xqIU6H5f%fengguang.wu@intel.com> (raw)
In-Reply-To: <1511767181-22793-4-git-send-email-rppt@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hi Andrei,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.15-rc1 next-20171128]
[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/Mike-Rapoport/vm-add-a-syscall-to-map-a-process-memory-into-a-pipe/20171128-182837
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/intel/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=xtensa
All warnings (new ones prefixed by >>):
>> <stdin>:1332:2: warning: #warning syscall process_vmsplice not implemented [-Wcpp]
---
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: 52627 bytes --]
next prev parent reply other threads:[~2017-11-28 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 7:19 [PATCH v4 0/4] vm: add a syscall to map a process memory into a pipe Mike Rapoport
2017-11-27 7:19 ` [PATCH v4 1/4] fs/splice: introduce pages_to_pipe helper Mike Rapoport
2017-11-27 7:19 ` [PATCH v4 2/4] vm: add a syscall to map a process memory into a pipe Mike Rapoport
2017-11-27 23:42 ` Andrew Morton
2017-11-29 7:42 ` Andrei Vagin
2017-11-27 7:19 ` [PATCH v4 3/4] x86: wire up the process_vmsplice syscall Mike Rapoport
2017-11-28 12:35 ` kbuild test robot [this message]
2017-11-27 7:19 ` [PATCH v4 4/4] test: add a test for " Mike Rapoport
2017-11-27 7:20 ` [PATCH] process_vmsplice.2: New page describing process_vmsplice(2) system call Mike Rapoport
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=201711282047.xqIU6H5f%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=avagin@openvz.org \
--cc=criu@openvz.org \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=josh@joshtriplett.org \
--cc=kbuild-all@01.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).