From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org
Subject: [ath6kl:master] BUILD SUCCESS e4c950b77a4d3fa9f4e43ad47eb8243f845dd17b
Date: Wed, 02 Sep 2020 08:48:29 +0800 [thread overview]
Message-ID: <5f4eebdd.kenJf+OGVNNsqVG4%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git master
branch HEAD: e4c950b77a4d3fa9f4e43ad47eb8243f845dd17b Add localversion-wireless-testing-ath
elapsed time: 727m
configs tested: 105
configs skipped: 5
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
s390 zfcpdump_defconfig
arm pxa_defconfig
arm gemini_defconfig
microblaze nommu_defconfig
arm spear6xx_defconfig
sh apsh4ad0a_defconfig
ia64 zx1_defconfig
powerpc mpc866_ads_defconfig
mips omega2p_defconfig
sh titan_defconfig
sparc alldefconfig
mips ip32_defconfig
riscv defconfig
powerpc pq2fads_defconfig
m68k mvme16x_defconfig
mips loongson3_defconfig
i386 defconfig
s390 debug_defconfig
mips tb0219_defconfig
sh sh7710voipgw_defconfig
mips tb0287_defconfig
mips cu1000-neo_defconfig
mips malta_defconfig
powerpc gamecube_defconfig
sh kfr2r09_defconfig
c6x defconfig
arm aspeed_g5_defconfig
sh migor_defconfig
m68k stmark2_defconfig
x86_64 defconfig
arm qcom_defconfig
mips rm200_defconfig
arc haps_hs_defconfig
powerpc ppc64e_defconfig
arm ixp4xx_defconfig
mips cobalt_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x 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
i386 allyesconfig
sparc allyesconfig
sparc defconfig
mips allyesconfig
mips allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a004-20200901
i386 randconfig-a005-20200901
i386 randconfig-a006-20200901
i386 randconfig-a002-20200901
i386 randconfig-a001-20200901
i386 randconfig-a003-20200901
i386 randconfig-a016-20200901
i386 randconfig-a015-20200901
i386 randconfig-a011-20200901
i386 randconfig-a013-20200901
i386 randconfig-a014-20200901
i386 randconfig-a012-20200901
x86_64 randconfig-a004-20200901
x86_64 randconfig-a006-20200901
x86_64 randconfig-a003-20200901
x86_64 randconfig-a005-20200901
x86_64 randconfig-a001-20200901
x86_64 randconfig-a002-20200901
riscv allyesconfig
riscv allnoconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a013-20200901
x86_64 randconfig-a016-20200901
x86_64 randconfig-a011-20200901
x86_64 randconfig-a012-20200901
x86_64 randconfig-a015-20200901
x86_64 randconfig-a014-20200901
---
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-09-02 0: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=5f4eebdd.kenJf+OGVNNsqVG4%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