From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/timers] BUILD SUCCESS 455f9075f14484f358b3c1d6845b4a438de198a7
Date: Tue, 30 Apr 2024 19:04:59 +0800 [thread overview]
Message-ID: <202404301956.NoXv7HKj-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/timers
branch HEAD: 455f9075f14484f358b3c1d6845b4a438de198a7 x86/tsc: Trust initial offset in architectural TSC-adjust MSRs
elapsed time: 803m
configs tested: 97
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 allmodconfig gcc
arc allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm neponset_defconfig gcc
arm64 allnoconfig gcc
arm64 defconfig gcc
csky allmodconfig gcc
csky allnoconfig gcc
csky allyesconfig gcc
csky defconfig gcc
i386 allmodconfig gcc
i386 allnoconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-001-20240430 gcc
i386 buildonly-randconfig-002-20240430 clang
i386 buildonly-randconfig-003-20240430 gcc
i386 buildonly-randconfig-004-20240430 clang
i386 buildonly-randconfig-005-20240430 clang
i386 buildonly-randconfig-006-20240430 gcc
i386 defconfig clang
i386 randconfig-001-20240430 clang
i386 randconfig-002-20240430 gcc
i386 randconfig-003-20240430 gcc
i386 randconfig-004-20240430 gcc
i386 randconfig-005-20240430 gcc
i386 randconfig-006-20240430 gcc
i386 randconfig-011-20240430 gcc
i386 randconfig-012-20240430 clang
i386 randconfig-013-20240430 clang
i386 randconfig-014-20240430 gcc
i386 randconfig-015-20240430 gcc
i386 randconfig-016-20240430 gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch allyesconfig gcc
loongarch defconfig 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 allmodconfig gcc
mips allnoconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
openrisc allmodconfig gcc
openrisc allnoconfig gcc
openrisc allyesconfig gcc
openrisc defconfig gcc
parisc allmodconfig gcc
parisc allnoconfig gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc ppa8548_defconfig gcc
powerpc ppc64e_defconfig gcc
powerpc tqm5200_defconfig gcc
riscv allnoconfig gcc
sh allnoconfig gcc
sh defconfig gcc
sh se7722_defconfig gcc
sh se7780_defconfig gcc
sh sh03_defconfig gcc
sparc allnoconfig gcc
sparc allyesconfig gcc
sparc defconfig gcc
sparc64 defconfig gcc
um allyesconfig gcc
um i386_defconfig gcc
x86_64 allnoconfig clang
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20240430 gcc
x86_64 defconfig gcc
x86_64 randconfig-003-20240430 gcc
x86_64 randconfig-004-20240430 gcc
x86_64 randconfig-005-20240430 gcc
x86_64 randconfig-013-20240430 gcc
x86_64 randconfig-075-20240430 gcc
x86_64 rhel-8.3-bpf gcc
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
xtensa allnoconfig gcc
xtensa allyesconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-30 11:05 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=202404301956.NoXv7HKj-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®