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 ad1f357157aa20466b590638f8a6d252d3cf33bc
Date: Sun, 02 May 2021 01:25:52 +0800 [thread overview]
Message-ID: <608d8f20.hsAMh7OJyXU94kh+%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: ad1f357157aa20466b590638f8a6d252d3cf33bc Merge branch 'clocksource.2021.04.30b' into HEAD
elapsed time: 742m
configs tested: 103
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
i386 allyesconfig
riscv allyesconfig
mips loongson1b_defconfig
powerpc rainier_defconfig
mips capcella_defconfig
arm colibri_pxa270_defconfig
sh kfr2r09-romimage_defconfig
arm lart_defconfig
microblaze mmu_defconfig
arm spear13xx_defconfig
arm gemini_defconfig
powerpc pq2fads_defconfig
ia64 defconfig
s390 allyesconfig
h8300 defconfig
ia64 tiger_defconfig
mips jmr3927_defconfig
m68k bvme6000_defconfig
ia64 bigsur_defconfig
mips vocore2_defconfig
parisc defconfig
s390 alldefconfig
mips ath79_defconfig
m68k stmark2_defconfig
h8300 h8s-sim_defconfig
mips ip27_defconfig
m68k m5407c3_defconfig
sh edosk7760_defconfig
sh secureedge5410_defconfig
arm mv78xx0_defconfig
ia64 allmodconfig
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
s390 allmodconfig
parisc allyesconfig
s390 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20210430
x86_64 randconfig-a004-20210430
x86_64 randconfig-a002-20210430
x86_64 randconfig-a006-20210430
x86_64 randconfig-a001-20210430
x86_64 randconfig-a005-20210430
i386 randconfig-a004-20210430
i386 randconfig-a001-20210430
i386 randconfig-a003-20210430
i386 randconfig-a002-20210430
i386 randconfig-a005-20210430
i386 randconfig-a006-20210430
i386 randconfig-a013-20210501
i386 randconfig-a015-20210501
i386 randconfig-a016-20210501
i386 randconfig-a014-20210501
i386 randconfig-a011-20210501
i386 randconfig-a012-20210501
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
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-a011-20210430
x86_64 randconfig-a016-20210430
x86_64 randconfig-a013-20210430
x86_64 randconfig-a014-20210430
x86_64 randconfig-a012-20210430
x86_64 randconfig-a015-20210430
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-05-01 17:26 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=608d8f20.hsAMh7OJyXU94kh+%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
all inboxes | Powered by JetHome®