From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:master] BUILD SUCCESS 0fded1f6a0d28e12f7835a62eb3ceda9762a86e9
Date: Fri, 07 Aug 2020 21:57:34 +0800 [thread overview]
Message-ID: <5f2d5dce.p1AOHuDTry/RKGQ+%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
branch HEAD: 0fded1f6a0d28e12f7835a62eb3ceda9762a86e9 Merge branch 'locking/urgent'
elapsed time: 722m
configs tested: 108
configs skipped: 6
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
sh polaris_defconfig
powerpc64 defconfig
microblaze mmu_defconfig
mips tb0287_defconfig
sh dreamcast_defconfig
mips fuloong2e_defconfig
mips loongson1c_defconfig
arm lpd270_defconfig
c6x dsk6455_defconfig
powerpc storcenter_defconfig
m68k m5275evb_defconfig
arm colibri_pxa270_defconfig
ia64 gensparse_defconfig
arm orion5x_defconfig
m68k m5475evb_defconfig
powerpc mvme5100_defconfig
riscv alldefconfig
sh sdk7786_defconfig
mips bmips_be_defconfig
s390 debug_defconfig
sh se7722_defconfig
ia64 zx1_defconfig
mips decstation_r4k_defconfig
openrisc or1ksim_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k 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
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20200807
i386 randconfig-a004-20200807
i386 randconfig-a001-20200807
i386 randconfig-a002-20200807
i386 randconfig-a003-20200807
i386 randconfig-a006-20200807
i386 randconfig-a005-20200806
i386 randconfig-a004-20200806
i386 randconfig-a001-20200806
i386 randconfig-a002-20200806
i386 randconfig-a003-20200806
i386 randconfig-a006-20200806
i386 randconfig-a005-20200805
i386 randconfig-a004-20200805
i386 randconfig-a001-20200805
i386 randconfig-a003-20200805
i386 randconfig-a002-20200805
i386 randconfig-a006-20200805
x86_64 randconfig-a013-20200807
x86_64 randconfig-a011-20200807
x86_64 randconfig-a012-20200807
x86_64 randconfig-a016-20200807
x86_64 randconfig-a015-20200807
x86_64 randconfig-a014-20200807
i386 randconfig-a011-20200807
i386 randconfig-a012-20200807
i386 randconfig-a013-20200807
i386 randconfig-a015-20200807
i386 randconfig-a014-20200807
i386 randconfig-a016-20200807
i386 randconfig-a011-20200805
i386 randconfig-a012-20200805
i386 randconfig-a013-20200805
i386 randconfig-a014-20200805
i386 randconfig-a015-20200805
i386 randconfig-a016-20200805
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-07 14:09 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=5f2d5dce.p1AOHuDTry/RKGQ+%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®