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 2cca53604b7465a1bddfd7ac6da076c12924c94d
Date: Fri, 17 Feb 2023 20:32:07 +0800 [thread overview]
Message-ID: <63ef73c7.kHsUt5frLgvX+1mt%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: 2cca53604b7465a1bddfd7ac6da076c12924c94d locktorture: With nested locks, occasionally skip main lock
elapsed time: 1057m
configs tested: 48
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
alpha allyesconfig
alpha defconfig
arc allyesconfig
arc defconfig
arm allmodconfig
arm allyesconfig
arm defconfig
arm64 allyesconfig
arm64 defconfig
csky defconfig
i386 allyesconfig
i386 debian-10.3
i386 defconfig
ia64 allmodconfig
ia64 defconfig
loongarch allmodconfig
loongarch allnoconfig
loongarch defconfig
m68k allmodconfig
m68k defconfig
mips allmodconfig
mips allyesconfig
nios2 defconfig
parisc defconfig
parisc64 defconfig
powerpc allmodconfig
powerpc allnoconfig
riscv allmodconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
s390 allmodconfig
s390 allyesconfig
s390 defconfig
sh allmodconfig
sparc defconfig
um i386_defconfig
um x86_64_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 kexec
x86_64 randconfig-a011-20230213
x86_64 randconfig-a012-20230213
x86_64 randconfig-a013-20230213
x86_64 randconfig-a014-20230213
x86_64 randconfig-a015-20230213
x86_64 randconfig-a016-20230213
x86_64 rhel-8.3
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-17 12:32 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=63ef73c7.kHsUt5frLgvX+1mt%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®