From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [rcu:dev.2021.03.02a] BUILD SUCCESS 00e647ff05e3e3cc31be250b9a762727e3c210c2
Date: Fri, 05 Mar 2021 04:25:42 +0800 [thread overview]
Message-ID: <60414246.pvObGH91NLAOKHfZ%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2021.03.02a
branch HEAD: 00e647ff05e3e3cc31be250b9a762727e3c210c2 kcsan, debugfs: Move debugfs file creation out of early init
elapsed time: 721m
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
arm axm55xx_defconfig
arm mvebu_v5_defconfig
powerpc acadia_defconfig
arc nsimosci_defconfig
arm pxa_defconfig
xtensa virt_defconfig
powerpc allyesconfig
powerpc mpc8313_rdb_defconfig
powerpc icon_defconfig
mips tb0287_defconfig
m68k m5307c3_defconfig
arc nsimosci_hs_smp_defconfig
arm imote2_defconfig
s390 debug_defconfig
mips bigsur_defconfig
arc hsdk_defconfig
sparc64 defconfig
powerpc storcenter_defconfig
powerpc akebono_defconfig
powerpc mpc8272_ads_defconfig
powerpc mpc834x_itxgp_defconfig
mips vocore2_defconfig
mips mpc30x_defconfig
mips lemote2f_defconfig
m68k allyesconfig
m68k m5407c3_defconfig
arm64 alldefconfig
mips rb532_defconfig
arm trizeps4_defconfig
powerpc mpc8315_rdb_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 tinyconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20210304
x86_64 randconfig-a001-20210304
x86_64 randconfig-a004-20210304
x86_64 randconfig-a005-20210304
x86_64 randconfig-a002-20210304
x86_64 randconfig-a003-20210304
i386 randconfig-a005-20210304
i386 randconfig-a003-20210304
i386 randconfig-a002-20210304
i386 randconfig-a004-20210304
i386 randconfig-a006-20210304
i386 randconfig-a001-20210304
i386 randconfig-a016-20210304
i386 randconfig-a012-20210304
i386 randconfig-a013-20210304
i386 randconfig-a014-20210304
i386 randconfig-a011-20210304
i386 randconfig-a015-20210304
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a013-20210304
x86_64 randconfig-a016-20210304
x86_64 randconfig-a015-20210304
x86_64 randconfig-a014-20210304
x86_64 randconfig-a012-20210304
x86_64 randconfig-a011-20210304
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-03-04 20:27 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=60414246.pvObGH91NLAOKHfZ%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®