From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org
Subject: [ath6kl:ath11k-qca6390-bringup] BUILD SUCCESS a9ce8040a968bdbb5aad2d767298d390e2507b16
Date: Fri, 20 Nov 2020 20:37:53 +0800 [thread overview]
Message-ID: <5fb7b8a1.yLsRYCtEVSgiLcs2%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath11k-qca6390-bringup
branch HEAD: a9ce8040a968bdbb5aad2d767298d390e2507b16 HACK: ath11k: add delays to suspend and resume handlers
elapsed time: 724m
configs tested: 103
configs skipped: 3
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
arm hackkit_defconfig
c6x evmc6678_defconfig
m68k amiga_defconfig
arm keystone_defconfig
mips tb0287_defconfig
m68k q40_defconfig
sh sh2007_defconfig
powerpc ppa8548_defconfig
arc nsimosci_defconfig
mips cu1830-neo_defconfig
arm bcm2835_defconfig
mips rm200_defconfig
powerpc rainier_defconfig
powerpc tqm8540_defconfig
arm trizeps4_defconfig
arm davinci_all_defconfig
powerpc powernv_defconfig
m68k sun3x_defconfig
arm exynos_defconfig
mips pistachio_defconfig
mips nlm_xlp_defconfig
powerpc mpc866_ads_defconfig
mips omega2p_defconfig
sh se7712_defconfig
arm badge4_defconfig
arm zeus_defconfig
arc haps_hs_defconfig
arm s5pv210_defconfig
powerpc eiger_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a006-20201119
i386 randconfig-a005-20201119
i386 randconfig-a002-20201119
i386 randconfig-a001-20201119
i386 randconfig-a003-20201119
i386 randconfig-a004-20201119
x86_64 randconfig-a015-20201119
x86_64 randconfig-a014-20201119
x86_64 randconfig-a011-20201119
x86_64 randconfig-a013-20201119
x86_64 randconfig-a016-20201119
x86_64 randconfig-a012-20201119
i386 randconfig-a012-20201119
i386 randconfig-a014-20201119
i386 randconfig-a016-20201119
i386 randconfig-a011-20201119
i386 randconfig-a013-20201119
i386 randconfig-a015-20201119
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a005-20201119
x86_64 randconfig-a003-20201119
x86_64 randconfig-a004-20201119
x86_64 randconfig-a002-20201119
x86_64 randconfig-a006-20201119
x86_64 randconfig-a001-20201119
---
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:[~2020-11-20 12:38 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=5fb7b8a1.yLsRYCtEVSgiLcs2%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