From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: [wireless-next:main] BUILD REGRESSION 90883c513ca01e77c56b8d94be7de11420c1dacf
Date: Sat, 25 Jul 2026 12:56:37 +0800 [thread overview]
Message-ID: <202607251212.6TdnMBFC-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
branch HEAD: 90883c513ca01e77c56b8d94be7de11420c1dacf Merge tag 'ath-next-20260722' of git://git.kernel.org/pub/scm/linux/kernel/git/ath/ath
Unverified Error/Warning (likely false positive, kindly check if interested):
drivers/net/wireless/nxp/nxpwifi/scan.c:2034:1: internal compiler error: in final_scan_insn_1, at final.cc:2823
Error/Warning ids grouped by kconfigs:
recent_errors
`-- csky-allmodconfig
`-- drivers-net-wireless-nxp-nxpwifi-scan.c:internal-compiler-error:in-final_scan_insn_1-at-final.cc
elapsed time: 802m
configs tested: 59
configs skipped: 1
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
arc randconfig-001-20260725 gcc-11.5.0
arc randconfig-002-20260725 gcc-8.5.0
arm randconfig-001-20260725 gcc-8.5.0
arm randconfig-002-20260725 clang-21
arm randconfig-003-20260725 gcc-10.5.0
arm randconfig-004-20260725 gcc-15.2.0
arm64 randconfig-001-20260725 clang-24
arm64 randconfig-002-20260725 gcc-13.4.0
arm64 randconfig-003-20260725 clang-24
arm64 randconfig-004-20260725 clang-24
csky allmodconfig gcc-16.1.0
csky randconfig-001-20260725 gcc-9.5.0
csky randconfig-002-20260725 gcc-16.1.0
hexagon randconfig-001 clang-17
hexagon randconfig-001-20260725 clang-17
hexagon randconfig-002-20260725 clang-24
i386 allmodconfig gcc-14
loongarch defconfig clang-24
loongarch randconfig-001-20260725 gcc-16.1.0
loongarch randconfig-002-20260725 gcc-13.4.0
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-001-20260725 gcc-11.5.0
nios2 randconfig-002-20260725 gcc-9.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc defconfig gcc-16.1.0
parisc randconfig-001-20260725 gcc-10.5.0
parisc randconfig-002-20260725 gcc-12.5.0
powerpc randconfig-001-20260725 gcc-9.5.0
powerpc randconfig-002-20260725 gcc-15.2.0
powerpc sam440ep_defconfig gcc-16.1.0
powerpc64 randconfig-001-20260725 clang-17
powerpc64 randconfig-002-20260725 clang-24
riscv randconfig-001-20260725 gcc-8.5.0
riscv randconfig-002-20260725 gcc-8.5.0
s390 randconfig-001-20260725 gcc-10.5.0
s390 randconfig-002-20260725 gcc-16.1.0
sh defconfig gcc-16.1.0
sh randconfig-001-20260725 gcc-16.1.0
sh randconfig-002-20260725 gcc-11.5.0
sparc randconfig-001-20260725 gcc-16.1.0
sparc randconfig-002-20260725 gcc-8.5.0
sparc64 randconfig-001-20260725 gcc-8.5.0
sparc64 randconfig-002-20260725 gcc-10.5.0
um randconfig-001-20260725 gcc-14
um randconfig-002-20260725 clang-24
x86_64 randconfig-001-20260725 gcc-14
x86_64 randconfig-002-20260725 clang-22
x86_64 randconfig-003-20260725 clang-22
x86_64 randconfig-004-20260725 clang-22
x86_64 randconfig-005-20260725 clang-22
x86_64 randconfig-006-20260725 clang-22
xtensa randconfig-002-20260725 gcc-8.5.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-25 4: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=202607251212.6TdnMBFC-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
/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.