From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [powerpc:merge] BUILD SUCCESS 8d4e8a236506000f4802d83e507c2e61cfabc69a
Date: Sat, 04 Sep 2021 11:38:33 +0800 [thread overview]
Message-ID: <6132ea39.YDc5Fr+0swo7Cnwd%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git merge
branch HEAD: 8d4e8a236506000f4802d83e507c2e61cfabc69a powerpc/ci: Disable corenet32_smp_defconfig on clang / GCC 4.9
elapsed time: 927m
configs tested: 104
configs skipped: 3
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
powerpc tqm5200_defconfig
sh sh7770_generic_defconfig
arm colibri_pxa270_defconfig
arm simpad_defconfig
sh urquell_defconfig
microblaze mmu_defconfig
xtensa nommu_kc705_defconfig
powerpc mpc866_ads_defconfig
powerpc mpc8313_rdb_defconfig
arm pxa255-idp_defconfig
ia64 bigsur_defconfig
powerpc akebono_defconfig
powerpc pasemi_defconfig
sh microdev_defconfig
mips maltaaprp_defconfig
powerpc mpc85xx_cds_defconfig
x86_64 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
xtensa allyesconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20210904
x86_64 randconfig-a004-20210904
x86_64 randconfig-a003-20210904
x86_64 randconfig-a005-20210904
x86_64 randconfig-a001-20210904
x86_64 randconfig-a002-20210904
x86_64 randconfig-a016-20210903
x86_64 randconfig-a011-20210903
x86_64 randconfig-a012-20210903
x86_64 randconfig-a015-20210903
x86_64 randconfig-a014-20210903
x86_64 randconfig-a013-20210903
arc randconfig-r043-20210904
riscv randconfig-r042-20210903
s390 randconfig-r044-20210903
arc randconfig-r043-20210903
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
um x86_64_defconfig
um i386_defconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
clang tested configs:
i386 randconfig-a005-20210903
i386 randconfig-a004-20210903
i386 randconfig-a006-20210903
i386 randconfig-a002-20210903
i386 randconfig-a001-20210903
i386 randconfig-a003-20210903
x86_64 randconfig-a011-20210904
x86_64 randconfig-a016-20210904
x86_64 randconfig-a012-20210904
x86_64 randconfig-a015-20210904
x86_64 randconfig-a014-20210904
x86_64 randconfig-a013-20210904
i386 randconfig-a012-20210904
i386 randconfig-a015-20210904
i386 randconfig-a011-20210904
i386 randconfig-a013-20210904
i386 randconfig-a014-20210904
i386 randconfig-a016-20210904
hexagon randconfig-r045-20210903
hexagon randconfig-r041-20210903
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-09-04 3: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=6132ea39.YDc5Fr+0swo7Cnwd%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