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 fe3e0a13e597c1c8617814bf9b42ab732db5c26e
Date: Thu, 06 Jul 2023 06:37:28 +0800 [thread overview]
Message-ID: <202307060626.FTV3vOGG-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: fe3e0a13e597c1c8617814bf9b42ab732db5c26e x86/xen: Fix secondary processors' FPU initialization
elapsed time: 721m
configs tested: 65
configs skipped: 91
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arc nsimosci_hs_defconfig gcc
arm allyesconfig gcc
arm collie_defconfig clang
arm defconfig clang
arm imx_v4_v5_defconfig clang
arm milbeaut_m10v_defconfig clang
arm mv78xx0_defconfig clang
arm s5pv210_defconfig clang
arm sama7_defconfig clang
arm socfpga_defconfig clang
arm vt8500_v6_v7_defconfig clang
i386 alldefconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-r004-20230705 gcc
i386 buildonly-randconfig-r005-20230705 gcc
i386 buildonly-randconfig-r006-20230705 gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i001-20230705 gcc
i386 randconfig-i002-20230705 gcc
i386 randconfig-i003-20230705 gcc
i386 randconfig-i004-20230705 gcc
i386 randconfig-i005-20230705 gcc
i386 randconfig-i006-20230705 gcc
i386 randconfig-i011-20230705 clang
i386 randconfig-i012-20230705 clang
i386 randconfig-i013-20230705 clang
i386 randconfig-i014-20230705 clang
i386 randconfig-i015-20230705 clang
i386 randconfig-i016-20230705 clang
m68k m5272c3_defconfig gcc
m68k multi_defconfig gcc
m68k mvme147_defconfig gcc
mips cu1000-neo_defconfig clang
mips malta_defconfig clang
powerpc g5_defconfig clang
powerpc lite5200b_defconfig clang
powerpc ppc44x_defconfig clang
powerpc ppc64e_defconfig clang
powerpc xes_mpc85xx_defconfig clang
riscv nommu_virt_defconfig clang
s390 allmodconfig gcc
sh sh7785lcr_32bit_defconfig gcc
sparc sparc32_defconfig gcc
x86_64 allyesconfig gcc
x86_64 buildonly-randconfig-r001-20230705 gcc
x86_64 buildonly-randconfig-r002-20230705 gcc
x86_64 buildonly-randconfig-r003-20230705 gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-r024-20230705 clang
x86_64 randconfig-x001-20230705 clang
x86_64 randconfig-x002-20230705 clang
x86_64 randconfig-x003-20230705 clang
x86_64 randconfig-x004-20230705 clang
x86_64 randconfig-x005-20230705 clang
x86_64 randconfig-x006-20230705 clang
x86_64 randconfig-x011-20230705 gcc
x86_64 randconfig-x012-20230705 gcc
x86_64 randconfig-x013-20230705 gcc
x86_64 randconfig-x014-20230705 gcc
x86_64 randconfig-x015-20230705 gcc
x86_64 randconfig-x016-20230705 gcc
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-05 22:38 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=202307060626.FTV3vOGG-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®