From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/misc] BUILD SUCCESS 86e39b94cd71a4987f9b98dd2a7d6c826e1c5c98
Date: Tue, 01 Oct 2024 16:29:50 +0800 [thread overview]
Message-ID: <202410011642.LVyByJde-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/misc
branch HEAD: 86e39b94cd71a4987f9b98dd2a7d6c826e1c5c98 x86/bugs: Correct RSB terminology in Kconfig
elapsed time: 878m
configs tested: 77
configs skipped: 129
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-14.1.0
alpha allyesconfig clang-20
arc allnoconfig gcc-14.1.0
arc axs103_defconfig gcc-14.1.0
arm allnoconfig gcc-14.1.0
arm collie_defconfig gcc-14.1.0
arm davinci_all_defconfig gcc-14.1.0
arm lpc18xx_defconfig gcc-14.1.0
arm versatile_defconfig gcc-14.1.0
arm64 allnoconfig gcc-14.1.0
csky allnoconfig gcc-14.1.0
hexagon allmodconfig clang-20
hexagon allnoconfig gcc-14.1.0
hexagon allyesconfig clang-20
i386 allmodconfig clang-18
i386 allmodconfig gcc-12
i386 allnoconfig clang-18
i386 allnoconfig gcc-12
i386 allyesconfig clang-18
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20241001 clang-18
i386 buildonly-randconfig-002-20241001 gcc-12
i386 buildonly-randconfig-003-20241001 clang-18
i386 buildonly-randconfig-004-20241001 gcc-12
i386 buildonly-randconfig-005-20241001 clang-18
i386 buildonly-randconfig-006-20241001 gcc-12
i386 defconfig clang-18
i386 randconfig-001-20241001 gcc-12
i386 randconfig-002-20241001 clang-18
i386 randconfig-003-20241001 clang-18
i386 randconfig-004-20241001 gcc-12
i386 randconfig-005-20241001 clang-18
i386 randconfig-006-20241001 clang-18
i386 randconfig-011-20241001 gcc-12
i386 randconfig-012-20241001 gcc-12
i386 randconfig-013-20241001 gcc-12
i386 randconfig-014-20241001 gcc-11
i386 randconfig-015-20241001 gcc-12
i386 randconfig-016-20241001 gcc-12
loongarch allmodconfig gcc-14.1.0
loongarch allnoconfig gcc-14.1.0
m68k allmodconfig gcc-14.1.0
m68k allnoconfig gcc-14.1.0
m68k allyesconfig gcc-14.1.0
microblaze allmodconfig gcc-14.1.0
microblaze allnoconfig gcc-14.1.0
microblaze allyesconfig gcc-14.1.0
mips allnoconfig gcc-14.1.0
mips db1xxx_defconfig gcc-14.1.0
mips rs90_defconfig gcc-14.1.0
nios2 allnoconfig gcc-14.1.0
openrisc allnoconfig clang-20
openrisc or1klitex_defconfig gcc-14.1.0
parisc allnoconfig clang-20
powerpc allnoconfig clang-20
powerpc canyonlands_defconfig gcc-14.1.0
powerpc cell_defconfig gcc-14.1.0
powerpc fsp2_defconfig gcc-14.1.0
powerpc mpc834x_itxgp_defconfig gcc-14.1.0
powerpc wii_defconfig gcc-14.1.0
riscv allnoconfig clang-20
s390 allnoconfig clang-20
sh alldefconfig gcc-14.1.0
sh allnoconfig gcc-14.1.0
sh ecovec24-romimage_defconfig gcc-14.1.0
sh titan_defconfig gcc-14.1.0
sh ul2_defconfig gcc-14.1.0
um allmodconfig clang-20
um allnoconfig clang-20
um allyesconfig clang-20
x86_64 allnoconfig clang-18
x86_64 allyesconfig clang-18
x86_64 defconfig clang-18
x86_64 defconfig gcc-11
x86_64 rhel-8.3 gcc-12
x86_64 rhel-8.3-rust clang-18
xtensa allnoconfig gcc-14.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-01 8:30 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=202410011642.LVyByJde-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