From: kernel test robot <lkp@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-wireless@vger.kernel.org
Subject: [mac80211-next:master] BUILD SUCCESS e5795aacd71b697c739f2d193b0e275993d93187
Date: Sun, 13 Dec 2020 17:28:44 +0800 [thread overview]
Message-ID: <5fd5decc.K+92xzlaUg9ViA0h%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
branch HEAD: e5795aacd71b697c739f2d193b0e275993d93187 Merge tag 'wireless-drivers-next-2020-12-12' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
elapsed time: 723m
configs tested: 106
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
nios2 alldefconfig
sh polaris_defconfig
m68k mvme16x_defconfig
openrisc defconfig
mips qi_lb60_defconfig
arm tegra_defconfig
mips rm200_defconfig
sh j2_defconfig
powerpc pseries_defconfig
mips bcm63xx_defconfig
mips nlm_xlp_defconfig
arm shmobile_defconfig
powerpc linkstation_defconfig
sh apsh4ad0a_defconfig
arc tb10x_defconfig
riscv allnoconfig
arm multi_v5_defconfig
sh defconfig
powerpc pcm030_defconfig
m68k atari_defconfig
mips loongson3_defconfig
powerpc amigaone_defconfig
powerpc ebony_defconfig
x86_64 defconfig
alpha allyesconfig
mips maltasmvp_defconfig
arc nsimosci_hs_smp_defconfig
powerpc mpc832x_mds_defconfig
powerpc currituck_defconfig
arm pxa910_defconfig
arm imote2_defconfig
parisc generic-32bit_defconfig
csky defconfig
arm multi_v4t_defconfig
sh ecovec24_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
alpha defconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 tinyconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20201213
x86_64 randconfig-a006-20201213
x86_64 randconfig-a002-20201213
x86_64 randconfig-a005-20201213
x86_64 randconfig-a004-20201213
x86_64 randconfig-a001-20201213
i386 randconfig-a001-20201213
i386 randconfig-a004-20201213
i386 randconfig-a003-20201213
i386 randconfig-a002-20201213
i386 randconfig-a005-20201213
i386 randconfig-a006-20201213
i386 randconfig-a014-20201213
i386 randconfig-a013-20201213
i386 randconfig-a012-20201213
i386 randconfig-a011-20201213
i386 randconfig-a016-20201213
i386 randconfig-a015-20201213
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv defconfig
riscv rv32_defconfig
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-a016-20201213
x86_64 randconfig-a012-20201213
x86_64 randconfig-a013-20201213
x86_64 randconfig-a015-20201213
x86_64 randconfig-a014-20201213
x86_64 randconfig-a011-20201213
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-12-13 9:30 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=5fd5decc.K+92xzlaUg9ViA0h%lkp@intel.com \
--to=lkp@intel.com \
--cc=kuba@kernel.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).