From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:rcu/next] BUILD SUCCESS 3c597738435cba984b3e3459d87bd5dec4d84e83
Date: Sat, 04 Feb 2023 11:58:09 +0800 [thread overview]
Message-ID: <63ddd7d1.zn4Hre7CDfX1J2GF%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: 3c597738435cba984b3e3459d87bd5dec4d84e83 doc: Update whatisRCU.rst
elapsed time: 747m
configs tested: 56
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
x86_64 allnoconfig
um i386_defconfig
um x86_64_defconfig
powerpc allnoconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 allyesconfig
m68k allyesconfig
m68k allmodconfig
alpha allyesconfig
arc allyesconfig
sh allmodconfig
x86_64 rhel-8.3-bpf
x86_64 rhel-8.3-syz
mips allyesconfig
x86_64 rhel-8.3-kunit
powerpc allmodconfig
x86_64 rhel-8.3-kvm
x86_64 randconfig-a004
x86_64 randconfig-a002
x86_64 randconfig-a006
ia64 allmodconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
arc defconfig
s390 allmodconfig
alpha defconfig
s390 defconfig
s390 allyesconfig
i386 defconfig
riscv randconfig-r042-20230204
s390 randconfig-r044-20230204
arc randconfig-r043-20230204
powerpc taishan_defconfig
sparc sparc64_defconfig
sh sh2007_defconfig
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
i386 allyesconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
clang tested configs:
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a005
x86_64 rhel-8.3-rust
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
x86_64 randconfig-a012
x86_64 randconfig-a014
x86_64 randconfig-a016
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-04 3:59 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=63ddd7d1.zn4Hre7CDfX1J2GF%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®