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 373e715e31bf4e0f129befe87613a278fac228d3
Date: Wed, 02 Nov 2022 19:39:09 +0800 [thread overview]
Message-ID: <636256dd.eqvham6J+zgmbJtg%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: 373e715e31bf4e0f129befe87613a278fac228d3 x86/tdx: Panic on bad configs that #VE on "private" memory access
elapsed time: 721m
configs tested: 82
configs skipped: 76
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-kunit
x86_64 randconfig-a002
x86_64 rhel-8.3-syz
x86_64 randconfig-a006
x86_64 randconfig-a004
i386 randconfig-a014-20221031
i386 randconfig-a011-20221031
i386 randconfig-a012-20221031
i386 defconfig
i386 randconfig-a013-20221031
i386 randconfig-a015-20221031
i386 randconfig-a016-20221031
x86_64 randconfig-a013
x86_64 randconfig-a011
i386 allyesconfig
x86_64 randconfig-a015
x86_64 defconfig
x86_64 rhel-8.3
x86_64 allyesconfig
um x86_64_defconfig
um i386_defconfig
ia64 allmodconfig
x86_64 randconfig-k001-20221031
powerpc allnoconfig
mips allyesconfig
powerpc allmodconfig
sh allmodconfig
sparc allnoconfig
xtensa smp_lx200_defconfig
arm gemini_defconfig
sh kfr2r09-romimage_defconfig
xtensa common_defconfig
s390 defconfig
s390 allmodconfig
arc defconfig
alpha defconfig
s390 allyesconfig
m68k allyesconfig
m68k allmodconfig
arc allyesconfig
alpha allyesconfig
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
arm keystone_defconfig
powerpc stx_gp3_defconfig
arm cm_x300_defconfig
mips xway_defconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
i386 randconfig-c001
i386 randconfig-c001-20221031
powerpc arches_defconfig
powerpc klondike_defconfig
clang tested configs:
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a005
x86_64 randconfig-a012
i386 randconfig-a003-20221031
i386 randconfig-a002-20221031
i386 randconfig-a004-20221031
i386 randconfig-a001-20221031
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a006-20221031
i386 randconfig-a005-20221031
i386 randconfig-a002
i386 randconfig-a006
i386 randconfig-a004
arm vexpress_defconfig
powerpc ebony_defconfig
powerpc obs600_defconfig
hexagon randconfig-r041-20221102
hexagon randconfig-r045-20221102
riscv randconfig-r042-20221101
hexagon randconfig-r041-20221101
hexagon randconfig-r045-20221101
s390 randconfig-r044-20221101
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-11-02 11:40 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=636256dd.eqvham6J+zgmbJtg%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®