From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:smp/urgent] BUILD SUCCESS 35551efb155e3b83445a6c3f66cb498d5efc182c
Date: Sat, 25 Jul 2026 16:06:15 +0800 [thread overview]
Message-ID: <202607251604.ilFtf3m6-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/urgent
branch HEAD: 35551efb155e3b83445a6c3f66cb498d5efc182c smp: Make CSD lock acquisition atomic for debug mode
elapsed time: 1067m
configs tested: 32
configs skipped: 7
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
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
arc randconfig-001-20260725 gcc-11.5.0
arc randconfig-002-20260725 gcc-8.5.0
arm randconfig-001-20260725 gcc-8.5.0
arm randconfig-002-20260725 clang-21
arm randconfig-003-20260725 gcc-10.5.0
arm randconfig-004-20260725 gcc-15.2.0
csky allmodconfig gcc-16.1.0
csky randconfig-001-20260725 gcc-9.5.0
i386 allmodconfig gcc-14
i386 buildonly-randconfig-002-20260725 gcc-14
i386 buildonly-randconfig-005-20260725 gcc-14
i386 buildonly-randconfig-006-20260725 gcc-14
m68k m5249evb_defconfig gcc-16.1.0
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc defconfig gcc-16.1.0
parisc randconfig-001-20260725 gcc-10.5.0
s390 randconfig-001-20260725 gcc-10.5.0
sh defconfig gcc-16.1.0
sparc randconfig-002-20260725 gcc-8.5.0
sparc64 randconfig-002-20260725 gcc-10.5.0
x86_64 buildonly-randconfig-001 gcc-12
x86_64 buildonly-randconfig-004-20260725 gcc-12
x86_64 buildonly-randconfig-005-20260725 gcc-12
x86_64 buildonly-randconfig-006-20260725 gcc-14
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-25 8:09 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=202607251604.ilFtf3m6-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.