From: kernel test robot <lkp@intel.com>
To: Kalle Valo <quic_kvalo@quicinc.com>
Cc: ath10k@lists.infradead.org
Subject: [kvalo-ath:ath-qca] BUILD REGRESSION 16652f582f4b8b78e64846c532b28a59f6673629
Date: Fri, 08 Dec 2023 19:16:37 +0800 [thread overview]
Message-ID: <202312081934.VLIHIJkw-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-qca
branch HEAD: 16652f582f4b8b78e64846c532b28a59f6673629 Merge branch 'ath-next' into ath-qca
Error/Warning ids grouped by kconfigs:
clang_recent_errors
`-- i386-buildonly-randconfig-004-20231208
|-- drivers-base-platform-msi.c:error:field-has-incomplete-type-msi_alloc_info_t-(aka-struct-irq_alloc_info-)
|-- include-linux-gpio-driver.h:error:field-has-incomplete-type-msi_alloc_info_t-(aka-struct-irq_alloc_info-)
|-- kernel-irq-msi.c:error:incomplete-definition-of-type-struct-irq_alloc_info
|-- kernel-irq-msi.c:error:invalid-application-of-sizeof-to-an-incomplete-type-msi_alloc_info_t-(aka-struct-irq_alloc_info-)
`-- kernel-irq-msi.c:error:variable-has-incomplete-type-msi_alloc_info_t-(aka-struct-irq_alloc_info-)
elapsed time: 1485m
configs tested: 43
configs skipped: 0
tested configs:
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20231208 clang
i386 buildonly-randconfig-002-20231208 clang
i386 buildonly-randconfig-003-20231208 clang
i386 buildonly-randconfig-004-20231208 clang
i386 buildonly-randconfig-005-20231208 clang
i386 buildonly-randconfig-006-20231208 clang
i386 defconfig gcc
i386 randconfig-001-20231208 clang
i386 randconfig-002-20231208 clang
i386 randconfig-003-20231208 clang
i386 randconfig-004-20231208 clang
i386 randconfig-005-20231208 clang
i386 randconfig-006-20231208 clang
i386 randconfig-011-20231208 gcc
i386 randconfig-012-20231208 gcc
i386 randconfig-013-20231208 gcc
i386 randconfig-014-20231208 gcc
i386 randconfig-015-20231208 gcc
i386 randconfig-016-20231208 gcc
loongarch allmodconfig gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
microblaze allmodconfig gcc
microblaze allyesconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allyesconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
sh allmodconfig gcc
sh allyesconfig gcc
sparc allmodconfig gcc
sparc64 allmodconfig gcc
sparc64 allyesconfig gcc
um allmodconfig clang
um allyesconfig clang
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 defconfig gcc
x86_64 rhel-8.3-rust clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-08 11:17 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=202312081934.VLIHIJkw-lkp@intel.com \
--to=lkp@intel.com \
--cc=ath10k@lists.infradead.org \
--cc=quic_kvalo@quicinc.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