From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/urgent] BUILD SUCCESS 0c2f6d04619ec2b53ad4b0b591eafc9389786e86
Date: Sat, 01 Jun 2024 18:09:43 +0800 [thread overview]
Message-ID: <202406011841.3Agkafsx-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: 0c2f6d04619ec2b53ad4b0b591eafc9389786e86 x86/topology/intel: Unlock CPUID before evaluating anything
elapsed time: 891m
configs tested: 96
configs skipped: 135
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha allyesconfig gcc
alpha defconfig gcc
arc allnoconfig gcc
arc defconfig gcc
arc randconfig-001-20240601 gcc
arc randconfig-002-20240601 gcc
arm randconfig-003-20240601 gcc
arm randconfig-004-20240601 gcc
arm64 allnoconfig gcc
arm64 defconfig gcc
arm64 randconfig-001-20240601 gcc
arm64 randconfig-004-20240601 gcc
csky allnoconfig gcc
csky defconfig gcc
csky randconfig-001-20240601 gcc
csky randconfig-002-20240601 gcc
i386 allmodconfig gcc
i386 allnoconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-001-20240601 clang
i386 buildonly-randconfig-002-20240601 gcc
i386 buildonly-randconfig-003-20240601 gcc
i386 buildonly-randconfig-004-20240601 gcc
i386 buildonly-randconfig-005-20240601 gcc
i386 buildonly-randconfig-006-20240601 clang
i386 defconfig clang
i386 randconfig-001-20240601 clang
i386 randconfig-002-20240601 gcc
i386 randconfig-003-20240601 clang
i386 randconfig-004-20240601 gcc
i386 randconfig-005-20240601 clang
i386 randconfig-006-20240601 gcc
i386 randconfig-011-20240601 gcc
i386 randconfig-012-20240601 gcc
i386 randconfig-013-20240601 gcc
i386 randconfig-014-20240601 gcc
i386 randconfig-015-20240601 clang
i386 randconfig-016-20240601 clang
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
loongarch randconfig-001-20240601 gcc
loongarch randconfig-002-20240601 gcc
m68k allmodconfig gcc
m68k allnoconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
microblaze allmodconfig gcc
microblaze allnoconfig gcc
microblaze allyesconfig gcc
microblaze defconfig gcc
mips allnoconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
nios2 randconfig-001-20240601 gcc
nios2 randconfig-002-20240601 gcc
parisc randconfig-001-20240601 gcc
parisc randconfig-002-20240601 gcc
powerpc randconfig-001-20240601 gcc
powerpc randconfig-002-20240601 gcc
powerpc randconfig-003-20240601 gcc
powerpc64 randconfig-003-20240601 gcc
riscv randconfig-002-20240601 gcc
s390 randconfig-001-20240601 gcc
s390 randconfig-002-20240601 gcc
sh randconfig-001-20240601 gcc
sh randconfig-002-20240601 gcc
sparc64 randconfig-001-20240601 gcc
sparc64 randconfig-002-20240601 gcc
um allyesconfig gcc
um randconfig-001-20240601 gcc
x86_64 allnoconfig clang
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20240601 clang
x86_64 buildonly-randconfig-002-20240601 clang
x86_64 buildonly-randconfig-004-20240601 gcc
x86_64 buildonly-randconfig-005-20240601 clang
x86_64 buildonly-randconfig-006-20240601 gcc
x86_64 defconfig gcc
x86_64 randconfig-002-20240601 clang
x86_64 randconfig-003-20240601 clang
x86_64 randconfig-004-20240601 clang
x86_64 randconfig-006-20240601 clang
x86_64 randconfig-011-20240601 clang
x86_64 randconfig-012-20240601 clang
x86_64 randconfig-013-20240601 clang
x86_64 randconfig-071-20240601 clang
x86_64 randconfig-073-20240601 clang
x86_64 randconfig-075-20240601 clang
x86_64 rhel-8.3-rust clang
xtensa randconfig-001-20240601 gcc
xtensa randconfig-002-20240601 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-01 10:10 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=202406011841.3Agkafsx-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