From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org
Subject: [ath6kl:ath-qca] BUILD SUCCESS 1d4c65a2a967505435ca3c855ba2e672fe6e1e46
Date: Wed, 23 Jun 2021 11:47:15 +0800 [thread overview]
Message-ID: <60d2aec3.+GHILsRq3O9/5Tuc%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-qca
branch HEAD: 1d4c65a2a967505435ca3c855ba2e672fe6e1e46 Merge branch 'ath-next' into ath-qca
elapsed time: 724m
configs tested: 106
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
powerpc sam440ep_defconfig
sh se7705_defconfig
powerpc mpc834x_itxgp_defconfig
mips malta_defconfig
xtensa alldefconfig
powerpc makalu_defconfig
h8300 edosk2674_defconfig
sh se7724_defconfig
arc tb10x_defconfig
sh polaris_defconfig
m68k apollo_defconfig
powerpc katmai_defconfig
h8300 alldefconfig
mips ip28_defconfig
arm eseries_pxa_defconfig
powerpc ep8248e_defconfig
sh rts7751r2dplus_defconfig
mips rbtx49xx_defconfig
sh se7343_defconfig
sh defconfig
arm mvebu_v5_defconfig
sh sh7770_generic_defconfig
powerpc kmeter1_defconfig
microblaze defconfig
arm orion5x_defconfig
arm rpc_defconfig
powerpc sequoia_defconfig
x86_64 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210622
i386 randconfig-a002-20210622
i386 randconfig-a003-20210622
i386 randconfig-a006-20210622
i386 randconfig-a005-20210622
i386 randconfig-a004-20210622
x86_64 randconfig-a012-20210622
x86_64 randconfig-a016-20210622
x86_64 randconfig-a015-20210622
x86_64 randconfig-a014-20210622
x86_64 randconfig-a013-20210622
x86_64 randconfig-a011-20210622
i386 randconfig-a014-20210622
i386 randconfig-a013-20210622
i386 randconfig-a015-20210622
i386 randconfig-a012-20210622
i386 randconfig-a016-20210622
i386 randconfig-a011-20210622
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
um kunit_defconfig
x86_64 defconfig
x86_64 kexec
x86_64 allyesconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
clang tested configs:
x86_64 randconfig-b001-20210622
x86_64 randconfig-a002-20210622
x86_64 randconfig-a001-20210622
x86_64 randconfig-a005-20210622
x86_64 randconfig-a003-20210622
x86_64 randconfig-a004-20210622
x86_64 randconfig-a006-20210622
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
reply other threads:[~2021-06-23 3:49 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=60d2aec3.+GHILsRq3O9/5Tuc%lkp@intel.com \
--to=lkp@intel.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).