From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:locking:urgent] BUILD SUCCESS a3b8d46fe401cba3a5c46dea610e6eb3dc15370e
Date: Mon, 07 Sep 2026 10:02:53 +0800 [thread overview]
Message-ID: <202609071051.9pAw7z7F-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent
branch HEAD: a3b8d46fe401cba3a5c46dea610e6eb3dc15370e futex: Prevent rcuwait use-after-free during requeue PI
elapsed time: 4037m
configs tested: 43
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
arc allnoconfig gcc-16.1.0
arc allyesconfig clang-24
arm allnoconfig gcc-16.1.0
arm64 allmodconfig clang-24
arm64 allnoconfig gcc-16.1.0
csky allmodconfig gcc-16.1.0
csky allnoconfig gcc-16.1.0
hexagon allmodconfig gcc-16.1.0
hexagon allnoconfig gcc-16.1.0
i386 allmodconfig clang-22
i386 allnoconfig gcc-16.1.0
i386 allyesconfig clang-22
loongarch allmodconfig clang-24
loongarch allnoconfig gcc-16.1.0
m68k allmodconfig gcc-16.1.0
m68k allnoconfig gcc-16.1.0
microblaze allnoconfig gcc-16.1.0
microblaze allyesconfig gcc-16.1.0
mips allnoconfig gcc-16.1.0
mips allyesconfig gcc-16.1.0
nios2 allmodconfig clang-20
nios2 allnoconfig clang-24
openrisc allmodconfig clang-20
openrisc allnoconfig clang-24
parisc allnoconfig clang-24
powerpc allnoconfig clang-24
riscv allmodconfig clang-24
riscv allnoconfig clang-24
s390 allnoconfig clang-24
sh allmodconfig gcc-16.1.0
sh allnoconfig clang-24
sparc allnoconfig clang-24
sparc64 allmodconfig clang-20
um allnoconfig clang-24
um allyesconfig gcc-16.1.0
x86_64 allmodconfig clang-22
x86_64 allnoconfig clang-24
x86_64 allyesconfig clang-22
x86_64 rhel-9.4-rust clang-22
xtensa allnoconfig clang-24
xtensa allyesconfig clang-20
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-07 2:03 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=202609071051.9pAw7z7F-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.