From: kernel test robot <lkp@intel.com>
To: Sumit Saxena <sumit.saxena@broadcom.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>
Subject: [linux-next:master 6711/7959] ./usr/include/scsi/scsi_bsg_mpi3mr.h:96:2: error: unknown type name '__le32'
Date: Sun, 1 May 2022 21:26:59 +0800 [thread overview]
Message-ID: <202205012134.OmrQqBxu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 5469f0c06732a077c70a759a81f2a1f00b277694
commit: 455aac4f7a13eced7697437f348b1287d6961838 [6711/7959] scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header
config: i386-randconfig-a006 (https://download.01.org/0day-ci/archive/20220501/202205012134.OmrQqBxu-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 400775649969b9baf3bc2a510266e7912bb16ae9)
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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=455aac4f7a13eced7697437f348b1287d6961838
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 455aac4f7a13eced7697437f348b1287d6961838
# save the config file
mkdir build_dir && cp config build_dir/.config
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>
Note: the linux-next/master HEAD 5469f0c06732a077c70a759a81f2a1f00b277694 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
>> ./usr/include/scsi/scsi_bsg_mpi3mr.h:96:2: error: unknown type name '__le32'
__le32 information_length;
^
>> ./usr/include/scsi/scsi_bsg_mpi3mr.h:97:2: error: unknown type name 'u8'
u8 driver_signature[12];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:98:2: error: unknown type name 'u8'
u8 os_name[16];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:99:2: error: unknown type name 'u8'
u8 os_version[12];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:100:2: error: unknown type name 'u8'
u8 driver_name[20];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:101:2: error: unknown type name 'u8'
u8 driver_version[32];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:102:2: error: unknown type name 'u8'
u8 driver_release_date[20];
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:103:2: error: unknown type name '__le32'
__le32 driver_capabilities;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:128:2: error: unknown type name 'uint32_t'
uint32_t adp_type;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:129:2: error: unknown type name 'uint32_t'
uint32_t rsvd1;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:130:2: error: unknown type name 'uint32_t'
uint32_t pci_dev_id;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:131:2: error: unknown type name 'uint32_t'
uint32_t pci_dev_hw_rev;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:132:2: error: unknown type name 'uint32_t'
uint32_t pci_subsys_dev_id;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:133:2: error: unknown type name 'uint32_t'
uint32_t pci_subsys_ven_id;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:134:2: error: unknown type name 'uint32_t'
uint32_t pci_dev:5;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:135:2: error: unknown type name 'uint32_t'
uint32_t pci_func:3;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:136:2: error: unknown type name 'uint32_t'
uint32_t pci_bus:8;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:137:2: error: unknown type name 'uint16_t'
uint16_t rsvd2;
^
./usr/include/scsi/scsi_bsg_mpi3mr.h:138:2: error: unknown type name 'uint32_t'
uint32_t pci_seg_id;
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-01 13:27 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=202205012134.OmrQqBxu-lkp@intel.com \
--to=lkp@intel.com \
--cc=himanshu.madhani@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@broadcom.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;
as well as URLs for NNTP newsgroup(s).