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 bf5641eccf71bcd13a849930e190563c3a19815d
Date: Wed, 31 Jul 2024 10:47:11 +0800 [thread overview]
Message-ID: <202407311008.U4PFsRJf-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: bf5641eccf71bcd13a849930e190563c3a19815d x86/CPU/AMD: Add models 0x60-0x6f to the Zen5 range
elapsed time: 737m
configs tested: 17
configs skipped: 127
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allmodconfig gcc-13
i386 allnoconfig gcc-13
i386 allyesconfig gcc-13
i386 buildonly-randconfig-001-20240731 clang-18
i386 buildonly-randconfig-003-20240731 clang-18
i386 buildonly-randconfig-004-20240731 gcc-13
i386 defconfig clang-18
openrisc allnoconfig gcc-14.1.0
parisc allnoconfig gcc-14.1.0
powerpc allnoconfig gcc-14.1.0
riscv allnoconfig gcc-14.1.0
s390 allnoconfig gcc-14.1.0
um allnoconfig gcc-14.1.0
x86_64 allnoconfig clang-18
x86_64 allyesconfig clang-18
x86_64 defconfig gcc-13
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-07-31 2:48 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=202407311008.U4PFsRJf-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