From: kernel test robot <lkp@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
Li Ming <ming.li@zohomail.com>
Subject: [djiang:cxl/fwctl 21/25] ./usr/include/fwctl/cxl.h:35:45: error: field 'get_feat_in' has incomplete type
Date: Fri, 14 Feb 2025 14:56:41 +0800 [thread overview]
Message-ID: <202502141428.z07ZTHVc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git cxl/fwctl
head: 368060188b78ad57197303bbffb78081837a7481
commit: 4c96849fd2546afeaa7696d4d267d3889a211cf7 [21/25] cxl: Add support to handle user feature commands for get feature
config: i386-buildonly-randconfig-002-20250214 (https://download.01.org/0day-ci/archive/20250214/202502141428.z07ZTHVc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502141428.z07ZTHVc-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/202502141428.z07ZTHVc-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <command-line>:
./usr/include/fwctl/cxl.h:34:50: error: field 'get_sup_feats_in' has incomplete type
34 | struct cxl_mbox_get_sup_feats_in get_sup_feats_in;
| ^~~~~~~~~~~~~~~~
>> ./usr/include/fwctl/cxl.h:35:45: error: field 'get_feat_in' has incomplete type
35 | struct cxl_mbox_get_feat_in get_feat_in;
| ^~~~~~~~~~~
./usr/include/fwctl/cxl.h:52:51: error: field 'get_feats_out' has incomplete type
52 | struct cxl_mbox_get_sup_feats_out get_feats_out;
| ^~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-14 6:57 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=202502141428.z07ZTHVc-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ming.li@zohomail.com \
--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 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.