From: kbuild test robot <lkp@intel.com>
To: Greg Kurz <groug@kaod.org>
Cc: kbuild-all@01.org, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, Eric Blake <eblake@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: wire up fchmodat2() syscall
Date: Wed, 1 Mar 2017 17:00:59 +0800 [thread overview]
Message-ID: <201703011603.nvjfMdnJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <148830143024.7103.7089323423307627106.stgit@bahia>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Hi Greg,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.10]
[cannot apply to next-20170228]
[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/Greg-Kurz/vfs-implement-fchmodat2-syscall/20170301-150213
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
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
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All warnings (new ones prefixed by >>):
>> <stdin>:1326:2: warning: #warning syscall fchmodat2 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: 49190 bytes --]
next prev parent reply other threads:[~2017-03-01 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 17:03 [PATCH 1/2] vfs: implement " Greg Kurz
2017-02-28 17:03 ` [PATCH 2/2] x86: wire up " Greg Kurz
2017-03-01 9:00 ` kbuild test robot [this message]
2017-02-28 18:23 ` [PATCH 1/2] vfs: implement " Eric Blake
2017-02-28 18:41 ` Greg Kurz
2017-02-28 18:59 ` Eric Blake
2017-04-11 17:52 ` Colin Walters
2017-04-11 17:55 ` Eric Blake
2017-04-11 18:07 ` Eric Blake
2017-04-11 18:08 ` Eric Blake
2017-04-11 19:09 ` Colin Walters
2017-04-19 12:45 ` Greg Kurz
2017-03-01 9:01 ` Michael Kerrisk
2017-04-11 11:39 ` Greg Kurz
2017-04-11 12:04 ` Greg Kurz
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=201703011603.nvjfMdnJ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=eblake@redhat.com \
--cc=groug@kaod.org \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®