From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/merge] BUILD SUCCESS f72ec8989cd1591b1c567b336e0bb4a78536ce39
Date: Thu, 11 Apr 2024 07:05:20 +0800 [thread overview]
Message-ID: <202404110718.b64GzeMx-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/merge
branch HEAD: f72ec8989cd1591b1c567b336e0bb4a78536ce39 Merge branch 'x86/cleanups' into x86/merge, to resolve conflict
elapsed time: 1127m
configs tested: 101
configs skipped: 138
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
arc haps_hs_smp_defconfig gcc
arc nsimosci_hs_defconfig gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm keystone_defconfig gcc
arm64 allnoconfig gcc
arm64 allyesconfig clang
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-20240410 gcc
i386 buildonly-randconfig-001-20240411 clang
i386 buildonly-randconfig-002-20240411 clang
i386 buildonly-randconfig-003-20240411 clang
i386 buildonly-randconfig-004-20240410 clang
i386 buildonly-randconfig-004-20240411 clang
i386 buildonly-randconfig-005-20240410 gcc
i386 buildonly-randconfig-005-20240411 clang
i386 buildonly-randconfig-006-20240410 gcc
i386 buildonly-randconfig-006-20240411 clang
i386 defconfig clang
i386 randconfig-002-20240410 clang
i386 randconfig-003-20240410 gcc
i386 randconfig-003-20240411 clang
i386 randconfig-004-20240410 gcc
i386 randconfig-004-20240411 clang
i386 randconfig-005-20240410 gcc
i386 randconfig-006-20240410 clang
i386 randconfig-006-20240411 clang
i386 randconfig-011-20240410 clang
i386 randconfig-011-20240411 clang
i386 randconfig-012-20240410 clang
i386 randconfig-013-20240410 gcc
i386 randconfig-014-20240410 clang
i386 randconfig-015-20240410 gcc
i386 randconfig-015-20240411 clang
i386 randconfig-016-20240410 gcc
i386 randconfig-016-20240411 clang
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
m68k allmodconfig gcc
m68k allnoconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
m68k sun3x_defconfig gcc
microblaze allmodconfig gcc
microblaze allnoconfig gcc
microblaze allyesconfig gcc
microblaze defconfig gcc
mips allnoconfig gcc
mips allyesconfig gcc
mips cu1830-neo_defconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
powerpc mpc832x_rdb_defconfig gcc
powerpc mvme5100_defconfig gcc
powerpc xes_mpc85xx_defconfig gcc
riscv allnoconfig gcc
s390 allyesconfig gcc
sh allmodconfig gcc
sh allnoconfig gcc
sh allyesconfig gcc
sh defconfig gcc
sh rsk7203_defconfig gcc
sh se7722_defconfig gcc
sparc allmodconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 alldefconfig gcc
sparc64 allmodconfig gcc
sparc64 allyesconfig gcc
sparc64 defconfig gcc
um allyesconfig gcc
um i386_defconfig 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 allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-10 23: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=202404110718.b64GzeMx-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