From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/core] BUILD SUCCESS 8f67d072aeb1598427bb0a6d823e265bb78ba534
Date: Fri, 12 Sep 2025 06:45:39 +0800 [thread overview]
Message-ID: <202509120629.1Q0mToBB-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/core
branch HEAD: 8f67d072aeb1598427bb0a6d823e265bb78ba534 Merge branch 'x86/bugs' into x86/core, to resolve conflict
elapsed time: 872m
configs tested: 72
configs skipped: 117
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig clang-22
arc allnoconfig clang-22
arc randconfig-001-20250912 clang-19
arc randconfig-002-20250912 clang-19
arm allnoconfig clang-22
arm randconfig-001-20250912 clang-19
arm randconfig-002-20250912 clang-19
arm randconfig-003-20250912 clang-19
arm randconfig-004-20250912 clang-19
arm64 allnoconfig clang-22
arm64 randconfig-001-20250912 clang-19
arm64 randconfig-002-20250912 clang-19
arm64 randconfig-003-20250912 clang-19
arm64 randconfig-004-20250912 clang-19
csky allnoconfig clang-22
hexagon allnoconfig clang-22
i386 allmodconfig clang-20
i386 allnoconfig clang-20
i386 allyesconfig clang-20
i386 buildonly-randconfig-001-20250911 clang-20
i386 buildonly-randconfig-001-20250912 gcc-13
i386 buildonly-randconfig-002-20250911 clang-20
i386 buildonly-randconfig-002-20250912 gcc-13
i386 buildonly-randconfig-003-20250911 clang-20
i386 buildonly-randconfig-003-20250912 gcc-13
i386 buildonly-randconfig-004-20250911 clang-20
i386 buildonly-randconfig-004-20250912 gcc-13
i386 buildonly-randconfig-005-20250911 clang-20
i386 buildonly-randconfig-005-20250912 gcc-13
i386 buildonly-randconfig-006-20250911 clang-20
i386 buildonly-randconfig-006-20250912 gcc-13
i386 defconfig clang-20
loongarch allnoconfig clang-22
m68k amiga_defconfig gcc-15.1.0
m68k mvme16x_defconfig gcc-15.1.0
microblaze defconfig gcc-15.1.0
nios2 defconfig gcc-15.1.0
openrisc allnoconfig clang-22
parisc allnoconfig clang-22
parisc defconfig gcc-15.1.0
parisc64 defconfig gcc-15.1.0
powerpc allnoconfig clang-22
powerpc ep8248e_defconfig gcc-15.1.0
powerpc mvme5100_defconfig gcc-15.1.0
powerpc stx_gp3_defconfig gcc-15.1.0
riscv allnoconfig clang-22
s390 allnoconfig clang-22
s390 zfcpdump_defconfig gcc-15.1.0
sh ap325rxa_defconfig gcc-15.1.0
sh se7721_defconfig gcc-15.1.0
sparc defconfig gcc-15.1.0
um allnoconfig clang-22
x86_64 allnoconfig clang-20
x86_64 allyesconfig clang-20
x86_64 buildonly-randconfig-001-20250911 gcc-14
x86_64 buildonly-randconfig-001-20250912 clang-20
x86_64 buildonly-randconfig-002-20250911 gcc-14
x86_64 buildonly-randconfig-002-20250912 clang-20
x86_64 buildonly-randconfig-003-20250911 clang-20
x86_64 buildonly-randconfig-003-20250912 clang-20
x86_64 buildonly-randconfig-004-20250911 clang-20
x86_64 buildonly-randconfig-004-20250912 clang-20
x86_64 buildonly-randconfig-005-20250911 clang-20
x86_64 buildonly-randconfig-005-20250912 clang-20
x86_64 buildonly-randconfig-006-20250911 gcc-14
x86_64 buildonly-randconfig-006-20250912 clang-20
x86_64 defconfig clang-20
x86_64 kexec clang-20
x86_64 rhel-9.4 clang-20
x86_64 rhel-9.4-func clang-20
x86_64 rhel-9.4-kselftests clang-20
x86_64 rhel-9.4-rust clang-20
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-11 22:45 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=202509120629.1Q0mToBB-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®