From: kernel test robot <lkp@intel.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: [wireless-drivers-next:pending] BUILD SUCCESS 19091b803d3735a84b9eaadd3b79e32c9731eed8
Date: Tue, 13 Apr 2021 07:56:20 +0800 [thread overview]
Message-ID: <6074de24.fpKAUoE4CUM0DcQT%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git pending
branch HEAD: 19091b803d3735a84b9eaadd3b79e32c9731eed8 Merge tag 'iwlwifi-next-for-kalle-2021-04-12' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next into pending
elapsed time: 727m
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
x86_64 allyesconfig
riscv allmodconfig
i386 allyesconfig
riscv allyesconfig
arm h3600_defconfig
x86_64 defconfig
xtensa defconfig
um kunit_defconfig
sh urquell_defconfig
powerpc linkstation_defconfig
mips malta_kvm_defconfig
arm rpc_defconfig
powerpc ppc64e_defconfig
arm oxnas_v6_defconfig
sh sh7724_generic_defconfig
sh sh03_defconfig
arm s5pv210_defconfig
powerpc tqm8540_defconfig
sh rts7751r2dplus_defconfig
mips maltaaprp_defconfig
arc axs103_smp_defconfig
mips db1xxx_defconfig
m68k m5249evb_defconfig
arm s3c2410_defconfig
mips loongson3_defconfig
sh landisk_defconfig
powerpc bamboo_defconfig
mips decstation_r4k_defconfig
arc haps_hs_smp_defconfig
sh se7712_defconfig
arm vexpress_defconfig
powerpc cell_defconfig
mips maltasmvp_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
s390 allmodconfig
parisc allyesconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a003-20210412
i386 randconfig-a001-20210412
i386 randconfig-a006-20210412
i386 randconfig-a005-20210412
i386 randconfig-a004-20210412
i386 randconfig-a002-20210412
x86_64 randconfig-a014-20210412
x86_64 randconfig-a015-20210412
x86_64 randconfig-a011-20210412
x86_64 randconfig-a013-20210412
x86_64 randconfig-a012-20210412
x86_64 randconfig-a016-20210412
i386 randconfig-a015-20210412
i386 randconfig-a014-20210412
i386 randconfig-a013-20210412
i386 randconfig-a012-20210412
i386 randconfig-a016-20210412
i386 randconfig-a011-20210412
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a003-20210412
x86_64 randconfig-a002-20210412
x86_64 randconfig-a001-20210412
x86_64 randconfig-a005-20210412
x86_64 randconfig-a006-20210412
x86_64 randconfig-a004-20210412
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-04-12 23:57 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=6074de24.fpKAUoE4CUM0DcQT%lkp@intel.com \
--to=lkp@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.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).