Messages in this thread | | | Date | Fri, 15 Oct 2021 19:43:36 +0800 | From | kernel test robot <> | Subject | Re: [PATCH] uapi: futex: Add a futex syscall |
| |
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 [unhandled content-type:application/gzip] | |