From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:lazy-obsolete.2022.11.30a] BUILD SUCCESS 45b1f52e5e9772ee4aa7e83af8f98328ead684fa
Date: Thu, 01 Dec 2022 18:13:36 +0800 [thread overview]
Message-ID: <63887e50.GlkCZ503e8qqSyZi%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git lazy-obsolete.2022.11.30a
branch HEAD: 45b1f52e5e9772ee4aa7e83af8f98328ead684fa rxrpc: Use call_rcu_hurry() instead of call_rcu()
elapsed time: 730m
configs tested: 47
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
x86_64 allnoconfig
s390 defconfig
s390 allmodconfig
arc defconfig
alpha defconfig
s390 allyesconfig
x86_64 rhel-8.3
um i386_defconfig
powerpc allnoconfig
um x86_64_defconfig
x86_64 defconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
x86_64 allyesconfig
ia64 allmodconfig
m68k allyesconfig
m68k allmodconfig
arc allyesconfig
alpha allyesconfig
sh allmodconfig
mips allyesconfig
powerpc allmodconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
i386 allyesconfig
i386 defconfig
clang tested configs:
s390 randconfig-r044-20221128
hexagon randconfig-r041-20221128
riscv randconfig-r042-20221128
hexagon randconfig-r045-20221128
x86_64 randconfig-k001-20221128
x86_64 randconfig-a011-20221128
x86_64 randconfig-a014-20221128
x86_64 randconfig-a012-20221128
x86_64 randconfig-a013-20221128
x86_64 randconfig-a016-20221128
x86_64 randconfig-a015-20221128
i386 randconfig-a014-20221128
i386 randconfig-a011-20221128
i386 randconfig-a013-20221128
i386 randconfig-a016-20221128
i386 randconfig-a012-20221128
i386 randconfig-a015-20221128
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-12-01 10:14 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=63887e50.GlkCZ503e8qqSyZi%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®