From: kernel test robot <lkp@intel.com>
To: "Bryan O'Donoghue" <bod@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [bod:qcom-laptops-v6.18-rc4-camss-icp-bps-ipe-icp-boots+stats-b4 121/121] usr/include/linux/videodev2.h:2550:20: error: field has incomplete type 'struct timespec'
Date: Sun, 05 Jul 2026 01:41:33 +0800 [thread overview]
Message-ID: <202607050136.f7zoWXgo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bod/linux.git qcom-laptops-v6.18-rc4-camss-icp-bps-ipe-icp-boots+stats-b4
head: ebd1e440443121d18f730ab2aeea5586a754f36f
commit: ebd1e440443121d18f730ab2aeea5586a754f36f [121/121] media: uapi: qcom-camss-stats-params
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20260705/202607050136.f7zoWXgo-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 0a2fb2a2269da0e2a3e230beb6cad39ca314db33)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260705/202607050136.f7zoWXgo-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/202607050136.f7zoWXgo-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:1:
In file included from ./usr/include/linux/media/qcom/camss/camss-stats-params.h:102:
>> usr/include/linux/videodev2.h:2550:20: error: field has incomplete type 'struct timespec'
2550 | struct timespec timestamp;
| ^
usr/include/linux/videodev2.h:2550:9: note: forward declaration of 'struct timespec'
2550 | struct timespec timestamp;
| ^
1 error generated.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-04 17:42 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=202607050136.f7zoWXgo-lkp@intel.com \
--to=lkp@intel.com \
--cc=bod@kernel.org \
--cc=llvm@lists.linux.dev \
--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