From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:master] BUILD SUCCESS f4fadf62be8da2e6d2d23519f21e17d0ff773113
Date: Fri, 01 Jul 2022 08:02:36 +0800 [thread overview]
Message-ID: <62be399c.lZkeU6cM1ok/uXbv%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
branch HEAD: f4fadf62be8da2e6d2d23519f21e17d0ff773113 Merge branch into tip/master: 'x86/vmware'
elapsed time: 854m
configs tested: 52
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm allyesconfig
arm64 allyesconfig
ia64 allmodconfig
arc allyesconfig
alpha allyesconfig
m68k allmodconfig
m68k allyesconfig
powerpc allnoconfig
powerpc allmodconfig
mips allyesconfig
sh allmodconfig
i386 defconfig
i386 allyesconfig
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
x86_64 randconfig-a013
x86_64 randconfig-a011
x86_64 randconfig-a015
i386 randconfig-a014
i386 randconfig-a012
i386 randconfig-a016
arc randconfig-r043-20220629
riscv randconfig-r042-20220629
s390 randconfig-r044-20220629
x86_64 randconfig-a004
x86_64 randconfig-a002
x86_64 randconfig-a006
um i386_defconfig
um x86_64_defconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 allyesconfig
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-func
clang tested configs:
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
x86_64 randconfig-a012
x86_64 randconfig-a016
x86_64 randconfig-a014
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
hexagon randconfig-r045-20220629
hexagon randconfig-r041-20220629
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a005
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-01 0:03 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=62be399c.lZkeU6cM1ok/uXbv%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).