From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: [mac80211-next:master] BUILD SUCCESS 8a16ffdc4cf37c1e6204054b0fb44052c8a48f0d
Date: Tue, 13 Apr 2021 07:56:22 +0800 [thread overview]
Message-ID: <6074de26.w7O7SdEcAG3AxPMb%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master
branch HEAD: 8a16ffdc4cf37c1e6204054b0fb44052c8a48f0d cfg80211: Remove wrong RNR IE validation check
elapsed time: 721m
configs tested: 111
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
nds32 alldefconfig
powerpc mpc834x_itx_defconfig
arc defconfig
sh apsh4a3a_defconfig
arm milbeaut_m10v_defconfig
arm nhk8815_defconfig
arc axs101_defconfig
powerpc tqm8541_defconfig
arm64 alldefconfig
m68k sun3x_defconfig
arm iop32x_defconfig
arm aspeed_g4_defconfig
arc nsimosci_hs_smp_defconfig
sh ecovec24-romimage_defconfig
arm mmp2_defconfig
arc nsim_700_defconfig
sh urquell_defconfig
powerpc linkstation_defconfig
mips malta_kvm_defconfig
arm rpc_defconfig
powerpc ppc64e_defconfig
arm oxnas_v6_defconfig
powerpc g5_defconfig
arm ixp4xx_defconfig
xtensa defconfig
sh ecovec24_defconfig
arm collie_defconfig
sh se7751_defconfig
powerpc cm5200_defconfig
x86_64 alldefconfig
arm ezx_defconfig
powerpc kmeter1_defconfig
arc haps_hs_smp_defconfig
sh se7712_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
xtensa allyesconfig
h8300 allyesconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
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 allyesconfig
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 defconfig
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=6074de26.w7O7SdEcAG3AxPMb%lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--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).