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 9543f6e26634537997b6e909c20911b7bf4876de
Date: Fri, 19 Apr 2024 11:53:53 +0800 [thread overview]
Message-ID: <202404191150.Ti8SYP95-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: 9543f6e26634537997b6e909c20911b7bf4876de x86/cpufeatures: Fix dependencies for GFNI, VAES, and VPCLMULQDQ
elapsed time: 736m
configs tested: 90
configs skipped: 136
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 axs103_defconfig gcc
arc defconfig gcc
arc randconfig-001-20240419 gcc
arc randconfig-002-20240419 gcc
arm ixp4xx_defconfig gcc
arm randconfig-001-20240419 gcc
arm randconfig-003-20240419 gcc
arm64 allmodconfig clang
arm64 allnoconfig gcc
arm64 allyesconfig clang
arm64 defconfig gcc
csky allnoconfig gcc
csky defconfig gcc
csky randconfig-001-20240419 gcc
csky randconfig-002-20240419 gcc
i386 allmodconfig gcc
i386 allnoconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-001-20240419 clang
i386 defconfig clang
i386 randconfig-001-20240419 clang
i386 randconfig-002-20240419 clang
i386 randconfig-003-20240419 clang
i386 randconfig-005-20240419 clang
i386 randconfig-006-20240419 clang
i386 randconfig-012-20240419 clang
i386 randconfig-014-20240419 clang
i386 randconfig-016-20240419 clang
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
loongarch randconfig-001-20240419 gcc
loongarch randconfig-002-20240419 gcc
m68k allmodconfig gcc
m68k allnoconfig gcc
m68k allyesconfig gcc
m68k bvme6000_defconfig gcc
m68k defconfig gcc
microblaze allmodconfig gcc
microblaze allnoconfig gcc
microblaze allyesconfig gcc
microblaze defconfig gcc
mips allnoconfig gcc
mips allyesconfig gcc
mips loongson1c_defconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
nios2 randconfig-001-20240419 gcc
nios2 randconfig-002-20240419 gcc
parisc randconfig-001-20240419 gcc
parisc randconfig-002-20240419 gcc
powerpc allyesconfig clang
powerpc mpc8313_rdb_defconfig gcc
powerpc ppa8548_defconfig gcc
powerpc ps3_defconfig gcc
powerpc randconfig-001-20240419 gcc
powerpc randconfig-002-20240419 gcc
powerpc randconfig-003-20240419 gcc
powerpc64 randconfig-001-20240419 gcc
powerpc64 randconfig-002-20240419 gcc
riscv allmodconfig clang
riscv allyesconfig clang
s390 allyesconfig gcc
s390 randconfig-002-20240419 gcc
sh allmodconfig gcc
sh allyesconfig gcc
sh espt_defconfig gcc
sh randconfig-001-20240419 gcc
sh randconfig-002-20240419 gcc
sh se7724_defconfig gcc
sparc allmodconfig gcc
sparc64 allmodconfig gcc
sparc64 allyesconfig gcc
sparc64 randconfig-001-20240419 gcc
sparc64 randconfig-002-20240419 gcc
um allyesconfig gcc
um randconfig-001-20240419 gcc
x86_64 allnoconfig clang
x86_64 allyesconfig clang
x86_64 defconfig gcc
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
xtensa randconfig-001-20240419 gcc
xtensa randconfig-002-20240419 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-19 3:54 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=202404191150.Ti8SYP95-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.