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 SUCCESS 8f9b07776fa51bed1b9b75b9bf052f495f1e58c1
Date: Tue, 16 Jan 2024 19:06:11 +0800 [thread overview]
Message-ID: <202401161909.OtTYMxEd-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-qca
branch HEAD: 8f9b07776fa51bed1b9b75b9bf052f495f1e58c1 Merge branch 'ath-next' into ath-qca
elapsed time: 2621m
configs tested: 86
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha defconfig gcc
arc allnoconfig gcc
arc defconfig gcc
arc randconfig-001-20240116 gcc
arc randconfig-002-20240116 gcc
arm allnoconfig gcc
arm defconfig clang
arm randconfig-001-20240116 clang
arm randconfig-002-20240116 clang
arm randconfig-003-20240116 clang
arm randconfig-004-20240116 clang
arm64 allnoconfig gcc
arm64 defconfig gcc
arm64 randconfig-001-20240116 clang
arm64 randconfig-002-20240116 clang
arm64 randconfig-004-20240116 clang
csky allnoconfig gcc
csky defconfig gcc
hexagon allnoconfig clang
hexagon defconfig clang
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20240115 gcc
i386 buildonly-randconfig-002-20240115 gcc
i386 buildonly-randconfig-003-20240115 gcc
i386 buildonly-randconfig-004-20240115 gcc
i386 buildonly-randconfig-005-20240115 gcc
i386 buildonly-randconfig-006-20240115 gcc
i386 defconfig gcc
i386 randconfig-001-20240115 gcc
i386 randconfig-002-20240115 gcc
i386 randconfig-003-20240115 gcc
i386 randconfig-004-20240115 gcc
i386 randconfig-005-20240115 gcc
i386 randconfig-006-20240115 gcc
i386 randconfig-011-20240115 clang
i386 randconfig-012-20240115 clang
i386 randconfig-013-20240115 clang
i386 randconfig-014-20240115 clang
i386 randconfig-015-20240115 clang
i386 randconfig-016-20240115 clang
loongarch allnoconfig gcc
loongarch defconfig gcc
m68k allnoconfig gcc
m68k defconfig gcc
microblaze allnoconfig gcc
microblaze defconfig gcc
mips allnoconfig clang
nios2 allnoconfig gcc
nios2 defconfig gcc
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
riscv allnoconfig clang
riscv defconfig gcc
s390 allmodconfig gcc
s390 allnoconfig gcc
s390 allyesconfig gcc
sh allmodconfig gcc
sh allyesconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20240116 clang
x86_64 buildonly-randconfig-002-20240116 clang
x86_64 buildonly-randconfig-003-20240116 clang
x86_64 buildonly-randconfig-004-20240116 clang
x86_64 buildonly-randconfig-005-20240116 clang
x86_64 buildonly-randconfig-006-20240116 clang
x86_64 defconfig gcc
x86_64 randconfig-001-20240116 gcc
x86_64 randconfig-002-20240116 gcc
x86_64 randconfig-003-20240116 gcc
x86_64 randconfig-004-20240116 gcc
x86_64 randconfig-005-20240116 gcc
x86_64 randconfig-006-20240116 gcc
x86_64 randconfig-011-20240116 clang
x86_64 randconfig-012-20240116 clang
x86_64 randconfig-013-20240116 clang
x86_64 randconfig-014-20240116 clang
x86_64 randconfig-015-20240116 clang
x86_64 rhel-8.3-rust clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-16 11:07 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=202401161909.OtTYMxEd-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 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.