From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [rcu:rcu/next] BUILD SUCCESS e107ca1a35b6fd9ec92fe4432bcb77e9284d821e
Date: Thu, 15 Jul 2021 19:57:10 +0800 [thread overview]
Message-ID: <60f02296.ORpAy5KoTqtl3XjY%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: e107ca1a35b6fd9ec92fe4432bcb77e9284d821e doc: Update stallwarn.rst with recent changes
elapsed time: 729m
configs tested: 102
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
m68k m5407c3_defconfig
mips malta_kvm_defconfig
arm sama5_defconfig
powerpc ppc64e_defconfig
arm badge4_defconfig
sh hp6xx_defconfig
arm omap2plus_defconfig
arm pleb_defconfig
xtensa iss_defconfig
arm oxnas_v6_defconfig
arc axs103_defconfig
arm tct_hammer_defconfig
mips decstation_defconfig
arc hsdk_defconfig
arm ezx_defconfig
openrisc simple_smp_defconfig
sh sh7757lcr_defconfig
powerpc storcenter_defconfig
powerpc pmac32_defconfig
openrisc or1ksim_defconfig
m68k amiga_defconfig
powerpc g5_defconfig
sparc alldefconfig
arm h5000_defconfig
powerpc cell_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
x86_64 allnoconfig
m68k defconfig
m68k allmodconfig
m68k allyesconfig
nds32 defconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allmodconfig
s390 defconfig
s390 allyesconfig
parisc allyesconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20210715
i386 randconfig-a006-20210715
i386 randconfig-a004-20210715
i386 randconfig-a001-20210715
i386 randconfig-a002-20210715
x86_64 randconfig-a013-20210715
x86_64 randconfig-a012-20210715
x86_64 randconfig-a015-20210715
x86_64 randconfig-a014-20210715
x86_64 randconfig-a016-20210715
x86_64 randconfig-a011-20210715
i386 randconfig-a014-20210715
i386 randconfig-a015-20210715
i386 randconfig-a011-20210715
i386 randconfig-a013-20210715
i386 randconfig-a012-20210715
i386 randconfig-a016-20210715
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-b001-20210715
x86_64 randconfig-a005-20210715
x86_64 randconfig-a004-20210715
x86_64 randconfig-a002-20210715
x86_64 randconfig-a003-20210715
x86_64 randconfig-a006-20210715
x86_64 randconfig-a001-20210715
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-07-15 11: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=60f02296.ORpAy5KoTqtl3XjY%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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).