From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/cache] BUILD SUCCESS a763fc24ecf2ef0471ccba3b1ff6e6271f4bdc0b
Date: Tue, 03 Dec 2024 11:36:59 +0800 [thread overview]
Message-ID: <202412031149.cskVYlKB-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/cache
branch HEAD: a763fc24ecf2ef0471ccba3b1ff6e6271f4bdc0b x86/resctrl: Use kthread_run_on_cpu()
elapsed time: 725m
configs tested: 70
configs skipped: 92
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-14.2.0
arc allnoconfig gcc-14.2.0
arc hsdk_defconfig gcc-14.2.0
arc randconfig-001-20241203 clang-20
arc randconfig-002-20241203 clang-20
arc vdk_hs38_smp_defconfig gcc-14.2.0
arm allnoconfig gcc-14.2.0
arm ep93xx_defconfig gcc-14.2.0
arm mv78xx0_defconfig gcc-14.2.0
arm randconfig-001-20241203 clang-20
arm randconfig-002-20241203 clang-20
arm randconfig-003-20241203 clang-20
arm randconfig-004-20241203 clang-20
arm stm32_defconfig gcc-14.2.0
arm64 allnoconfig gcc-14.2.0
arm64 randconfig-001-20241203 clang-20
arm64 randconfig-002-20241203 clang-20
arm64 randconfig-003-20241203 clang-20
arm64 randconfig-004-20241203 clang-20
csky alldefconfig gcc-14.2.0
csky allnoconfig gcc-14.2.0
hexagon allnoconfig gcc-14.2.0
i386 buildonly-randconfig-001-20241203 clang-19
i386 buildonly-randconfig-001-20241203 gcc-12
i386 buildonly-randconfig-002-20241203 clang-19
i386 buildonly-randconfig-002-20241203 gcc-12
i386 buildonly-randconfig-003-20241203 clang-19
i386 buildonly-randconfig-004-20241203 clang-19
i386 buildonly-randconfig-005-20241203 clang-19
i386 buildonly-randconfig-006-20241203 clang-19
i386 buildonly-randconfig-006-20241203 gcc-12
loongarch allnoconfig gcc-14.2.0
m68k allnoconfig gcc-14.2.0
m68k stmark2_defconfig gcc-14.2.0
microblaze allnoconfig gcc-14.2.0
mips allnoconfig gcc-14.2.0
mips cavium_octeon_defconfig gcc-14.2.0
mips eyeq5_defconfig gcc-14.2.0
nios2 alldefconfig gcc-14.2.0
nios2 allnoconfig gcc-14.2.0
openrisc allnoconfig clang-20
parisc allnoconfig clang-20
parisc generic-64bit_defconfig gcc-14.2.0
powerpc allnoconfig clang-20
powerpc asp8347_defconfig gcc-14.2.0
powerpc currituck_defconfig gcc-14.2.0
powerpc eiger_defconfig gcc-14.2.0
powerpc motionpro_defconfig gcc-14.2.0
powerpc tqm8541_defconfig gcc-14.2.0
riscv allnoconfig clang-20
s390 allnoconfig clang-20
sh allnoconfig gcc-14.2.0
sh edosk7760_defconfig gcc-14.2.0
sh kfr2r09-romimage_defconfig gcc-14.2.0
sh r7780mp_defconfig gcc-14.2.0
sh se7724_defconfig gcc-14.2.0
sh se7780_defconfig gcc-14.2.0
sh sh7763rdp_defconfig gcc-14.2.0
sh sh7785lcr_defconfig gcc-14.2.0
sh ul2_defconfig gcc-14.2.0
sparc allnoconfig gcc-14.2.0
um allnoconfig clang-20
x86_64 buildonly-randconfig-001-20241203 gcc-11
x86_64 buildonly-randconfig-002-20241203 gcc-11
x86_64 buildonly-randconfig-003-20241203 gcc-11
x86_64 buildonly-randconfig-004-20241203 gcc-11
x86_64 buildonly-randconfig-005-20241203 gcc-11
x86_64 buildonly-randconfig-006-20241203 gcc-11
xtensa allnoconfig gcc-14.2.0
xtensa virt_defconfig gcc-14.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-03 3:39 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=202412031149.cskVYlKB-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