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 ed1e745dafc282905e0a96ce8f4ce2f3c885f3ff
Date: Fri, 09 Jun 2023 04:05:36 +0800 [thread overview]
Message-ID: <202306090434.dw3l4raT-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/merge
branch HEAD: ed1e745dafc282905e0a96ce8f4ce2f3c885f3ff Merge branch 'x86/tdx' into x86/merge, to ease integration testing
elapsed time: 732m
configs tested: 90
configs skipped: 6
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
alpha defconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-r043-20230608 gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm randconfig-r023-20230608 gcc
arm randconfig-r024-20230608 gcc
arm randconfig-r046-20230608 gcc
arm64 allyesconfig gcc
arm64 buildonly-randconfig-r002-20230608 gcc
arm64 buildonly-randconfig-r004-20230608 gcc
arm64 defconfig gcc
arm64 randconfig-r034-20230608 gcc
csky defconfig gcc
hexagon randconfig-r041-20230608 clang
hexagon randconfig-r045-20230608 clang
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i005-20230608 gcc
i386 randconfig-i006-20230608 gcc
i386 randconfig-i016-20230608 clang
i386 randconfig-i051-20230608 gcc
i386 randconfig-i052-20230608 gcc
i386 randconfig-i053-20230608 gcc
i386 randconfig-i054-20230608 gcc
i386 randconfig-i055-20230608 gcc
i386 randconfig-i056-20230608 gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
loongarch randconfig-r004-20230608 gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
m68k randconfig-r021-20230608 gcc
mips allmodconfig gcc
mips allyesconfig gcc
mips buildonly-randconfig-r003-20230608 clang
mips randconfig-r002-20230608 clang
mips randconfig-r032-20230608 clang
nios2 defconfig gcc
nios2 randconfig-r013-20230608 gcc
nios2 randconfig-r014-20230608 gcc
openrisc randconfig-r025-20230608 gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc randconfig-r001-20230608 gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv allyesconfig gcc
riscv defconfig gcc
riscv randconfig-r012-20230608 clang
riscv randconfig-r015-20230608 clang
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-r016-20230608 clang
s390 randconfig-r035-20230608 gcc
sh allmodconfig gcc
sparc allyesconfig gcc
sparc defconfig gcc
sparc randconfig-r033-20230608 gcc
sparc64 randconfig-r011-20230608 gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allyesconfig gcc
x86_64 buildonly-randconfig-r005-20230608 gcc
x86_64 buildonly-randconfig-r006-20230608 gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a011-20230608 clang
x86_64 randconfig-a012-20230608 clang
x86_64 randconfig-a013-20230608 clang
x86_64 randconfig-a014-20230608 clang
x86_64 randconfig-a015-20230608 clang
x86_64 randconfig-a016-20230608 clang
x86_64 randconfig-r036-20230608 gcc
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
xtensa buildonly-randconfig-r001-20230608 gcc
xtensa randconfig-r005-20230608 gcc
xtensa randconfig-r022-20230608 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-08 20:06 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=202306090434.dw3l4raT-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;
as well as URLs for NNTP newsgroup(s).