From: kernel test robot <lkp@intel.com>
To: Alistair Francis <alistair.francis@opensource.wdc.com>,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
alistair23@gmail.com, arnd@arndb.de,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] uapi: futex: Add a futex syscall
Date: Fri, 15 Oct 2021 19:43:36 +0800 [thread overview]
Message-ID: <202110151905.yFBROWjZ-lkp@intel.com> (raw)
In-Reply-To: <20211015005923.2659140-1-alistair.francis@opensource.wdc.com>
[-- Attachment #1: Type: text/plain, Size: 4541 bytes --]
Hi Alistair,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on soc/for-next linus/master v5.15-rc5 next-20211013]
[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/uapi-futex-Add-a-futex-syscall/20211015-090054
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5816b3e6577eaa676ceb00a848f0fd65fe2adc29
config: x86_64-randconfig-r015-20211014 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project acb3b187c4c88650a6a717a1bcb234d27d0d7f54)
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
# https://github.com/0day-ci/linux/commit/38a003698424c55ceb42e9be69f47014a6b4f6bd
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alistair-Francis/uapi-futex-Add-a-futex-syscall/20211015-090054
git checkout 38a003698424c55ceb42e9be69f47014a6b4f6bd
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64
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 >>):
In file included from <built-in>:1:
./usr/include/linux/futex_syscall.h:19:36: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
futex_syscall_timeout(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
./usr/include/linux/futex_syscall.h:19:62: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
futex_syscall_timeout(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
>> ./usr/include/linux/futex_syscall.h:20:16: warning: declaration of 'struct timespec' will not be visible outside of this function [-Wvisibility]
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^
./usr/include/linux/futex_syscall.h:20:48: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
struct timespec *timeout, __volatile__ u_int32_t *uaddr2, int val3)
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
./usr/include/linux/futex_syscall.h:61:39: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
futex_syscall_nr_requeue(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
./usr/include/linux/futex_syscall.h:61:65: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
futex_syscall_nr_requeue(__volatile__ u_int32_t *uaddr, int op, u_int32_t val,
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
./usr/include/linux/futex_syscall.h:62:5: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
u_int32_t nr_requeue, __volatile__ u_int32_t *uaddr2, int val3)
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
./usr/include/linux/futex_syscall.h:62:40: error: unknown type name 'u_int32_t'; did you mean '__int128_t'?
u_int32_t nr_requeue, __volatile__ u_int32_t *uaddr2, int val3)
^~~~~~~~~
__int128_t
note: '__int128_t' declared here
1 warning and 7 errors generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35903 bytes --]
prev parent reply other threads:[~2021-10-15 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 0:59 Alistair Francis
2021-10-15 8:23 ` Arnd Bergmann
2021-10-18 3:41 ` Alistair Francis
2021-10-21 6:13 ` Arnd Bergmann
2021-10-15 11:43 ` kernel test robot [this message]
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=202110151905.yFBROWjZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=alistair.francis@opensource.wdc.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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®