From: kbuild test robot <lkp@intel.com>
To: Dave Watson <davejwatson@fb.com>
Cc: kbuild-all@01.org, davejwatson@fb.com, kernel-team@fb.com,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
pjt@google.com, mathieu.desnoyers@efficios.com
Subject: Re: [RFC PATCH 1/3] restartable sequences: user-space per-cpu critical sections
Date: Fri, 23 Oct 2015 03:35:27 +0800 [thread overview]
Message-ID: <201510230345.MJYgQ3C1%fengguang.wu@intel.com> (raw)
In-Reply-To: <581c0b6403285219724961a3d250c6d95dfacea7.1445464158.git.davejwatson@fb.com>
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
Hi Dave,
[auto build test ERROR on v4.3-rc6 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Dave-Watson/restartable-sequences-benchmarks/20151023-020939
config: openrisc-allmodconfig (attached as .config)
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=openrisc
All errors (new ones prefixed by >>):
In file included from include/asm-generic/unistd.h:1:0,
from arch/openrisc/include/uapi/asm/unistd.h:26,
from arch/openrisc/kernel/sys_call_table.c:27:
>> include/uapi/asm-generic/unistd.h:717:1: error: 'sys_restartable_sequences' undeclared here (not in a function)
vim +/sys_restartable_sequences +717 include/uapi/asm-generic/unistd.h
711 __SC_COMP(__NR_execveat, sys_execveat, compat_sys_execveat)
712 #define __NR_userfaultfd 282
713 __SYSCALL(__NR_userfaultfd, sys_userfaultfd)
714 #define __NR_membarrier 283
715 __SYSCALL(__NR_membarrier, sys_membarrier)
716 #define __NR_restartable_sequences 284
> 717 __SYSCALL(__NR_restartable_sequences, sys_restartable_sequences)
718
719 #undef __NR_syscalls
720 #define __NR_syscalls 285
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 35026 bytes --]
next prev parent reply other threads:[~2015-10-22 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:06 [RFC PATCH 0/3] restartable sequences benchmarks Dave Watson
2015-10-22 18:06 ` [RFC PATCH 1/3] restartable sequences: user-space per-cpu critical sections Dave Watson
2015-10-22 18:53 ` kbuild test robot
2015-10-22 19:35 ` kbuild test robot [this message]
2015-10-22 18:06 ` [RFC PATCH 2/3] restartable sequences: x86 ABI Dave Watson
2015-10-22 18:07 ` [RFC PATCH 3/3] restartable sequences: basic user-space self-tests Dave Watson
2015-10-22 19:11 ` [RFC PATCH 0/3] restartable sequences benchmarks Andy Lutomirski
2015-10-22 22:10 ` Dave Watson
-- strict thread matches above, loose matches on Subject: below --
2015-06-24 22:26 [RFC PATCH 0/3] restartable sequences: fast user-space percpu critical sections Paul Turner
2015-06-24 22:26 ` [RFC PATCH 1/3] restartable sequences: user-space per-cpu " Paul Turner
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=201510230345.MJYgQ3C1%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davejwatson@fb.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=pjt@google.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
all inboxes | Powered by JetHome®