From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-lts:5.10/KMB-yocto 8168/8457] ./usr/include/misc/xlink_uapi.h:51:19: error: a parameter list without types is only allowed in a function definition
Date: Fri, 10 Dec 2021 10:12:33 +0800 [thread overview]
Message-ID: <202112101046.cox5aeKQ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
tree: https://github.com/intel/linux-intel-lts.git 5.10/KMB-yocto
head: e00ba07ec4720ed356ee8a0ae9a1f53f754b7577
commit: da8a22c1d117dc7a34005542869efd709361b4d9 [8168/8457] xlink-core: Add Keem Bay XLink Core Module
config: i386-randconfig-a014-20211209 (https://download.01.org/0day-ci/archive/20211210/202112101046.cox5aeKQ-lkp(a)intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 097a1cb1d5ebb3a0ec4bcaed8ba3ff6a8e33c00a)
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/intel/linux-intel-lts/commit/da8a22c1d117dc7a34005542869efd709361b4d9
git remote add intel-lts https://github.com/intel/linux-intel-lts.git
git fetch --no-tags intel-lts 5.10/KMB-yocto
git checkout da8a22c1d117dc7a34005542869efd709361b4d9
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross 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 <built-in>:1:
>> ./usr/include/misc/xlink_uapi.h:51:19: error: a parameter list without types is only allowed in a function definition
void (*callback)(uint16_t);
^
1 error generated.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
reply other threads:[~2021-12-10 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202112101046.cox5aeKQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.