From: kernel test robot <lkp@intel.com>
To: Kalle Valo <quic_kvalo@quicinc.com>
Cc: ath10k@lists.infradead.org
Subject: [kvalo-ath:pending] BUILD SUCCESS 48150730ef38a1d5b551a69d6cf38dcdec6ae3bf
Date: Fri, 24 Nov 2023 19:06:05 +0800 [thread overview]
Message-ID: <202311241903.wE6BIf2w-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending
branch HEAD: 48150730ef38a1d5b551a69d6cf38dcdec6ae3bf wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus()
elapsed time: 2418m
configs tested: 66
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20231123 gcc
i386 buildonly-randconfig-002-20231123 gcc
i386 buildonly-randconfig-003-20231123 gcc
i386 buildonly-randconfig-004-20231123 gcc
i386 buildonly-randconfig-005-20231123 gcc
i386 buildonly-randconfig-006-20231123 gcc
i386 defconfig gcc
i386 randconfig-001-20231123 gcc
i386 randconfig-002-20231123 gcc
i386 randconfig-003-20231123 gcc
i386 randconfig-004-20231123 gcc
i386 randconfig-005-20231123 gcc
i386 randconfig-006-20231123 gcc
i386 randconfig-011-20231123 clang
i386 randconfig-012-20231123 clang
i386 randconfig-013-20231123 clang
i386 randconfig-014-20231123 clang
i386 randconfig-015-20231123 clang
i386 randconfig-016-20231123 clang
loongarch allmodconfig gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
microblaze allmodconfig gcc
microblaze allyesconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allyesconfig gcc
openrisc allyesconfig gcc
parisc allmodconfig gcc
parisc allyesconfig gcc
powerpc allmodconfig clang
powerpc allyesconfig clang
riscv allmodconfig gcc
riscv allyesconfig gcc
riscv rv32_defconfig clang
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20231123 gcc
x86_64 buildonly-randconfig-002-20231123 gcc
x86_64 buildonly-randconfig-003-20231123 gcc
x86_64 buildonly-randconfig-004-20231123 gcc
x86_64 buildonly-randconfig-005-20231123 gcc
x86_64 buildonly-randconfig-006-20231123 gcc
x86_64 defconfig gcc
x86_64 randconfig-001-20231123 clang
x86_64 randconfig-002-20231123 clang
x86_64 randconfig-003-20231123 clang
x86_64 randconfig-004-20231123 clang
x86_64 randconfig-005-20231123 clang
x86_64 randconfig-006-20231123 clang
x86_64 randconfig-011-20231123 gcc
x86_64 randconfig-012-20231123 gcc
x86_64 randconfig-013-20231123 gcc
x86_64 randconfig-014-20231123 gcc
x86_64 randconfig-015-20231123 gcc
x86_64 randconfig-016-20231123 gcc
x86_64 randconfig-071-20231123 gcc
x86_64 randconfig-072-20231123 gcc
x86_64 randconfig-073-20231123 gcc
x86_64 randconfig-074-20231123 gcc
x86_64 randconfig-075-20231123 gcc
x86_64 randconfig-076-20231123 gcc
x86_64 rhel-8.3-rust clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2023-11-24 11:06 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=202311241903.wE6BIf2w-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