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 d1fb034b75a8a96fcb4bf01a7c0e1421eef833a3
Date: Fri, 27 Sep 2024 15:08:10 +0800 [thread overview]
Message-ID: <202409271505.f1dOit4j-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: d1fb034b75a8a96fcb4bf01a7c0e1421eef833a3 x86/cpu: Add two Intel CPU model numbers
elapsed time: 754m
configs tested: 36
configs skipped: 133
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20240927 clang-18
i386 buildonly-randconfig-002-20240927 clang-18
i386 buildonly-randconfig-002-20240927 gcc-12
i386 buildonly-randconfig-003-20240927 clang-18
i386 buildonly-randconfig-004-20240927 clang-18
i386 buildonly-randconfig-005-20240927 clang-18
i386 buildonly-randconfig-006-20240927 clang-18
i386 buildonly-randconfig-006-20240927 gcc-12
i386 defconfig clang-18
i386 randconfig-001-20240927 clang-18
i386 randconfig-002-20240927 clang-18
i386 randconfig-003-20240927 clang-18
i386 randconfig-004-20240927 clang-18
i386 randconfig-004-20240927 gcc-12
i386 randconfig-005-20240927 clang-18
i386 randconfig-006-20240927 clang-18
i386 randconfig-011-20240927 clang-18
i386 randconfig-011-20240927 gcc-12
i386 randconfig-012-20240927 clang-18
i386 randconfig-013-20240927 clang-18
i386 randconfig-013-20240927 gcc-12
i386 randconfig-014-20240927 clang-18
i386 randconfig-014-20240927 gcc-12
i386 randconfig-015-20240927 clang-18
i386 randconfig-015-20240927 gcc-11
i386 randconfig-016-20240927 clang-18
x86_64 allnoconfig clang-18
x86_64 allyesconfig clang-18
x86_64 defconfig gcc-11
x86_64 kexec clang-18
x86_64 kexec gcc-12
x86_64 rhel-8.3 gcc-12
x86_64 rhel-8.3-rust clang-18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-27 7:09 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=202409271505.f1dOit4j-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