From: kernel test robot <lkp@intel.com>
To: Alistair Francis <alistair.francis@opensource.wdc.com>,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, jolsa@redhat.com, mingo@redhat.com,
dave@stgolabs.net, linux-perf-users@vger.kernel.org,
arnd@arndb.de, namhyung@kernel.org, alistair23@gmail.com,
mark.rutland@arm.com, tglx@linutronix.de
Subject: Re: [PATCH v4 3/6] uapi: futex: Add a futex syscall
Date: Sun, 5 Dec 2021 11:04:22 +0800 [thread overview]
Message-ID: <202112051113.Z2TMYJx9-lkp@intel.com> (raw)
In-Reply-To: <20211202111659.2077911-3-alistair.francis@opensource.wdc.com>
Hi Alistair,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/locking/core]
[also build test ERROR on linux/master soc/for-next linus/master v5.16-rc3 next-20211203]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Alistair-Francis/perf-bench-futex-Add-support-for-32-bit-systems-with-64-bit-time_t/20211202-192015
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 4e0d84634445ed550498d613a49ea8f6cfa5e66c
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20211205/202112051113.Z2TMYJx9-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/710fc0b1a255e93e04efbaccf76f6445db51ff1f
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alistair-Francis/perf-bench-futex-Add-support-for-32-bit-systems-with-64-bit-time_t/20211202-192015
git checkout 710fc0b1a255e93e04efbaccf76f6445db51ff1f
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:32:
./usr/include/linux/futex_syscall.h:33:16: warning: 'struct timespec' declared inside parameter list will not be visible outside of this definition or declaration
33 | struct timespec *timeout, __volatile__ uint32_t *uaddr2, int val3)
| ^~~~~~~~
./usr/include/linux/futex_syscall.h: In function '__kernel_futex_syscall_timeout':
>> ./usr/include/linux/futex_syscall.h:36:13: error: dereferencing pointer to incomplete type 'struct timespec'
36 | if (sizeof(*timeout) != sizeof(struct __kernel_old_timespec)) {
| ^~~~~~~~
>> ./usr/include/linux/futex_syscall.h:37:13: error: implicit declaration of function 'syscall' [-Werror=implicit-function-declaration]
37 | int ret = syscall(__NR_futex_time64, uaddr, op, val, timeout, uaddr2, val3);
| ^~~~~~~
cc1: some warnings being treated as errors
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-05 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 11:16 [PATCH v4 1/6] perf bench futex: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2021-12-02 11:16 ` [PATCH v4 2/6] selftests: futex: Call the futex syscall from a function Alistair Francis
2021-12-02 11:16 ` [PATCH v4 3/6] uapi: futex: Add a futex syscall Alistair Francis
2021-12-03 1:01 ` kernel test robot
2021-12-05 3:04 ` kernel test robot [this message]
2021-12-02 11:16 ` [PATCH v4 4/6] selftests: futex: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2021-12-02 11:16 ` [PATCH v4 5/6] uapi: futex: Add a futex waitv syscall Alistair Francis
2021-12-02 11:16 ` [PATCH v4 6/6] selftests: futex: Use futex_waitv helper function Alistair Francis
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=202112051113.Z2TMYJx9-lkp@intel.com \
--to=lkp@intel.com \
--cc=alistair.francis@opensource.wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=jolsa@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
/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).