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 bb3d086f7fba4430e643b6581c2d75f8c2e7765c
Date: Thu, 02 May 2024 03:17:56 +0800 [thread overview]
Message-ID: <202405020352.iaIKRQC9-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending
branch HEAD: bb3d086f7fba4430e643b6581c2d75f8c2e7765c wifi: ath10k: add LED and GPIO controlling support for various chipsets
elapsed time: 1769m
configs tested: 94
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha allyesconfig gcc
alpha defconfig gcc
arc allnoconfig gcc
arc defconfig gcc
arc randconfig-001-20240502 gcc
arc randconfig-002-20240502 gcc
arm allnoconfig clang
arm defconfig clang
arm randconfig-001-20240502 gcc
arm randconfig-002-20240502 gcc
arm randconfig-003-20240502 gcc
arm randconfig-004-20240502 gcc
arm64 allnoconfig gcc
arm64 defconfig gcc
arm64 randconfig-001-20240502 gcc
arm64 randconfig-002-20240502 clang
csky allnoconfig gcc
csky defconfig gcc
hexagon allmodconfig clang
hexagon allnoconfig clang
hexagon allyesconfig clang
hexagon defconfig clang
i386 allmodconfig gcc
i386 allnoconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-001-20240501 clang
i386 buildonly-randconfig-002-20240501 gcc
i386 buildonly-randconfig-003-20240501 clang
i386 buildonly-randconfig-004-20240501 gcc
i386 buildonly-randconfig-005-20240501 gcc
i386 buildonly-randconfig-006-20240501 clang
i386 defconfig clang
i386 randconfig-001-20240501 gcc
i386 randconfig-002-20240501 clang
i386 randconfig-003-20240501 gcc
i386 randconfig-004-20240501 gcc
i386 randconfig-005-20240501 clang
i386 randconfig-006-20240501 clang
i386 randconfig-011-20240501 gcc
i386 randconfig-012-20240501 gcc
i386 randconfig-013-20240501 gcc
i386 randconfig-014-20240501 gcc
i386 randconfig-015-20240501 gcc
i386 randconfig-016-20240501 gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
m68k allmodconfig gcc
m68k allnoconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
microblaze allmodconfig gcc
microblaze allnoconfig gcc
microblaze allyesconfig gcc
microblaze defconfig gcc
mips allnoconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
riscv allnoconfig gcc
riscv defconfig clang
s390 allmodconfig clang
s390 allnoconfig clang
s390 allyesconfig gcc
s390 defconfig clang
sh allmodconfig gcc
sh allnoconfig gcc
sh allyesconfig gcc
sh defconfig gcc
sparc allmodconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 allmodconfig gcc
sparc64 defconfig gcc
um allmodconfig clang
um allnoconfig clang
um allyesconfig gcc
um defconfig clang
um i386_defconfig gcc
um x86_64_defconfig clang
x86_64 allnoconfig clang
x86_64 allyesconfig clang
x86_64 defconfig gcc
x86_64 rhel-8.3-rust clang
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-01 19:18 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=202405020352.iaIKRQC9-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