From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [rcu:merge-example] BUILD SUCCESS d810e482ea8343a61c462f41b3afea64c8310916
Date: Wed, 30 Jun 2021 17:07:59 +0800 [thread overview]
Message-ID: <60dc346f.QlADBh60sIVHxPmb%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git merge-example
branch HEAD: d810e482ea8343a61c462f41b3afea64c8310916 Merge remote-tracking branch 'linus/master' into HEAD
elapsed time: 726m
configs tested: 107
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
arm colibri_pxa300_defconfig
powerpc64 defconfig
mips gpr_defconfig
powerpc ppc44x_defconfig
sh kfr2r09-romimage_defconfig
powerpc xes_mpc85xx_defconfig
sh se7724_defconfig
sh sdk7786_defconfig
powerpc taishan_defconfig
powerpc mpc885_ads_defconfig
arm zeus_defconfig
riscv nommu_k210_defconfig
arc haps_hs_defconfig
arm pxa255-idp_defconfig
powerpc tqm8540_defconfig
sh apsh4a3a_defconfig
csky defconfig
powerpc currituck_defconfig
powerpc powernv_defconfig
sh se7751_defconfig
mips qi_lb60_defconfig
powerpc pseries_defconfig
powerpc eiger_defconfig
x86_64 allnoconfig
arm spear3xx_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210628
i386 randconfig-a002-20210628
i386 randconfig-a003-20210628
i386 randconfig-a006-20210628
i386 randconfig-a005-20210628
i386 randconfig-a004-20210628
i386 randconfig-a002-20210629
i386 randconfig-a001-20210629
i386 randconfig-a003-20210629
i386 randconfig-a006-20210629
i386 randconfig-a005-20210629
i386 randconfig-a004-20210629
x86_64 randconfig-a012-20210628
x86_64 randconfig-a016-20210628
x86_64 randconfig-a015-20210628
x86_64 randconfig-a013-20210628
x86_64 randconfig-a014-20210628
x86_64 randconfig-a011-20210628
i386 randconfig-a011-20210628
i386 randconfig-a014-20210628
i386 randconfig-a013-20210628
i386 randconfig-a015-20210628
i386 randconfig-a016-20210628
i386 randconfig-a012-20210628
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
um kunit_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-20210628
x86_64 randconfig-a002-20210628
x86_64 randconfig-a005-20210628
x86_64 randconfig-a001-20210628
x86_64 randconfig-a003-20210628
x86_64 randconfig-a004-20210628
x86_64 randconfig-a006-20210628
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-06-30 9:08 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=60dc346f.QlADBh60sIVHxPmb%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®