From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/entry] BUILD SUCCESS adb334d17858d8b679a41f7f2cd230e5c6accc0a
Date: Sun, 02 Aug 2020 08:37:13 +0800 [thread overview]
Message-ID: <5f260ab9.GI8AxwoNwT41m8cD%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry
branch HEAD: adb334d17858d8b679a41f7f2cd230e5c6accc0a Merge branch 'WIP.x86/entry' into x86/entry, to merge the latest generic code and resolve conflicts
elapsed time: 2148m
configs tested: 85
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
xtensa xip_kc705_defconfig
arm versatile_defconfig
arm ezx_defconfig
powerpc maple_defconfig
arm pleb_defconfig
arm mmp2_defconfig
arm lpd270_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20200731
i386 randconfig-a004-20200731
i386 randconfig-a006-20200731
i386 randconfig-a002-20200731
i386 randconfig-a001-20200731
i386 randconfig-a003-20200731
i386 randconfig-a004-20200802
i386 randconfig-a005-20200802
i386 randconfig-a001-20200802
i386 randconfig-a002-20200802
i386 randconfig-a003-20200802
i386 randconfig-a006-20200802
i386 randconfig-a004-20200801
i386 randconfig-a005-20200801
i386 randconfig-a001-20200801
i386 randconfig-a003-20200801
i386 randconfig-a002-20200801
i386 randconfig-a006-20200801
x86_64 randconfig-a015-20200731
x86_64 randconfig-a014-20200731
x86_64 randconfig-a016-20200731
x86_64 randconfig-a012-20200731
x86_64 randconfig-a013-20200731
x86_64 randconfig-a011-20200731
i386 randconfig-a016-20200731
i386 randconfig-a012-20200731
i386 randconfig-a014-20200731
i386 randconfig-a015-20200731
i386 randconfig-a013-20200731
i386 randconfig-a011-20200731
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-08-02 0:38 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=5f260ab9.GI8AxwoNwT41m8cD%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®