From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [gustavoars:testing/wfamnae-next20251110 10/18] drivers/scsi/aic94xx/aic94xx_sas.h:323:35: error: field 'ssp_cmd' has incomplete type
Date: Tue, 11 Nov 2025 17:39:37 +0800 [thread overview]
Message-ID: <202511111702.50G2mceU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/wfamnae-next20251110
head: be928bdef109364ada67e15d004067a1770a36f0
commit: fc09359f7ea98c65bfc288e3e37dda0af71652f7 [10/18] scsi: libsas/aci94xx: Avoid multiple -Wflex-array-member-not-at-end warnings
config: sparc-allmodconfig (https://download.01.org/0day-ci/archive/20251111/202511111702.50G2mceU-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251111/202511111702.50G2mceU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511111702.50G2mceU-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/scsi/aic94xx/aic94xx_hwi.h:19,
from drivers/scsi/aic94xx/aic94xx_reg.h:13,
from drivers/scsi/aic94xx/aic94xx_init.c:21:
>> drivers/scsi/aic94xx/aic94xx_sas.h:323:35: error: field 'ssp_cmd' has incomplete type
323 | struct ssp_command_iu_hdr ssp_cmd;
| ^~~~~~~
vim +/ssp_cmd +323 drivers/scsi/aic94xx/aic94xx_sas.h
316
317 /* This is both ssp_task and long_ssp_task
318 */
319 struct initiate_ssp_task {
320 u8 proto_conn_rate; /* proto:6,4, conn_rate:3,0 */
321 __le32 total_xfer_len;
322 struct ssp_frame_hdr ssp_frame;
> 323 struct ssp_command_iu_hdr ssp_cmd;
324 __le16 sister_scb; /* 0xFFFF */
325 __le16 conn_handle; /* index to DDB for the intended target */
326 u8 data_dir; /* :1,0 */
327 #define DATA_DIR_NONE 0x00
328 #define DATA_DIR_IN 0x01
329 #define DATA_DIR_OUT 0x02
330 #define DATA_DIR_BYRECIPIENT 0x03
331
332 u8 _r_a;
333 u8 retry_count;
334 u8 _r_b[5];
335 struct sg_el sg_element[3]; /* 2 real and 1 link */
336 } __attribute__ ((packed));
337
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-11 9:40 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=202511111702.50G2mceU-lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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