From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [powerpc:next-test] BUILD SUCCESS 29b535f8c5da3984d083068bd651af0631dcdca6
Date: Sun, 25 Oct 2020 10:48:53 +0800 [thread overview]
Message-ID: <5f94e795.m6KYMRrdRyFilAaX%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test
branch HEAD: 29b535f8c5da3984d083068bd651af0631dcdca6 selftests/powerpc/eeh: disable kselftest timeout setting for eeh-basic
elapsed time: 965m
configs tested: 112
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
mips cu1830-neo_defconfig
powerpc bluestone_defconfig
powerpc mpc8272_ads_defconfig
arm tct_hammer_defconfig
powerpc canyonlands_defconfig
s390 zfcpdump_defconfig
mips malta_kvm_guest_defconfig
arm hackkit_defconfig
m68k m5249evb_defconfig
sh se7619_defconfig
sh hp6xx_defconfig
h8300 h8s-sim_defconfig
sh se7722_defconfig
powerpc allyesconfig
mips malta_qemu_32r6_defconfig
m68k multi_defconfig
powerpc mpc5200_defconfig
arm zx_defconfig
mips bcm47xx_defconfig
xtensa alldefconfig
xtensa nommu_kc705_defconfig
m68k m5407c3_defconfig
powerpc pseries_defconfig
arm tegra_defconfig
m68k m5272c3_defconfig
arm jornada720_defconfig
m68k apollo_defconfig
arm lart_defconfig
m68k allmodconfig
powerpc mpc834x_mds_defconfig
um kunit_defconfig
sh rts7751r2d1_defconfig
arm pxa_defconfig
mips tb0219_defconfig
arm shmobile_defconfig
sh sh03_defconfig
powerpc ppc6xx_defconfig
sparc64 alldefconfig
arm magician_defconfig
arm ezx_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
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 allmodconfig
powerpc allnoconfig
i386 randconfig-a002-20201024
i386 randconfig-a003-20201024
i386 randconfig-a005-20201024
i386 randconfig-a001-20201024
i386 randconfig-a006-20201024
i386 randconfig-a004-20201024
x86_64 randconfig-a013-20201024
x86_64 randconfig-a016-20201024
x86_64 randconfig-a015-20201024
x86_64 randconfig-a012-20201024
x86_64 randconfig-a014-20201024
x86_64 randconfig-a011-20201024
i386 randconfig-a016-20201024
i386 randconfig-a015-20201024
i386 randconfig-a014-20201024
i386 randconfig-a013-20201024
i386 randconfig-a012-20201024
i386 randconfig-a011-20201024
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_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
clang tested configs:
x86_64 randconfig-a001-20201024
x86_64 randconfig-a003-20201024
x86_64 randconfig-a002-20201024
x86_64 randconfig-a006-20201024
x86_64 randconfig-a005-20201024
x86_64 randconfig-a004-20201024
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-10-25 2:51 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=5f94e795.m6KYMRrdRyFilAaX%lkp@intel.com \
--to=lkp@intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).