From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:locking/core] BUILD SUCCESS c2df0a6af177b6c06a859806a876f92b072dc624
Date: Thu, 19 May 2022 11:30:19 +0800 [thread overview]
Message-ID: <6285b9cb.UgvxhIErda0NEjhh%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
branch HEAD: c2df0a6af177b6c06a859806a876f92b072dc624 locking/atomic/x86: Introduce arch_try_cmpxchg64
elapsed time: 1732m
configs tested: 58
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 defconfig
arm64 allyesconfig
arm allmodconfig
arm defconfig
arm allyesconfig
ia64 defconfig
ia64 allmodconfig
ia64 allyesconfig
m68k allyesconfig
m68k allmodconfig
m68k defconfig
alpha defconfig
csky defconfig
nios2 allyesconfig
alpha allyesconfig
arc defconfig
sh allmodconfig
h8300 allyesconfig
xtensa allyesconfig
s390 defconfig
s390 allmodconfig
parisc defconfig
parisc64 defconfig
parisc allyesconfig
s390 allyesconfig
sparc defconfig
i386 allyesconfig
sparc allyesconfig
i386 defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
nios2 defconfig
arc allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allnoconfig
powerpc allmodconfig
arc randconfig-r043-20220516
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv defconfig
riscv allnoconfig
riscv allmodconfig
riscv allyesconfig
um i386_defconfig
um x86_64_defconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-syz
x86_64 kexec
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3
clang tested configs:
hexagon randconfig-r045-20220516
hexagon randconfig-r041-20220516
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-19 3:31 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=6285b9cb.UgvxhIErda0NEjhh%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 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®