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 dc4225b1afe8424b3fdf56599cdac283be683c69
Date: Fri, 25 Jun 2021 11:50:09 +0800 [thread overview]
Message-ID: <60d55271.LB04gQHcrMrth91n%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git merge
branch HEAD: dc4225b1afe8424b3fdf56599cdac283be683c69 Automatic merge of 'next' into merge (2021-06-25 00:45)
elapsed time: 734m
configs tested: 105
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
sh kfr2r09-romimage_defconfig
sh ul2_defconfig
arm spear3xx_defconfig
alpha alldefconfig
m68k amiga_defconfig
powerpc ep8248e_defconfig
mips omega2p_defconfig
arm s5pv210_defconfig
powerpc akebono_defconfig
xtensa generic_kc705_defconfig
openrisc or1ksim_defconfig
ia64 allmodconfig
sh edosk7760_defconfig
powerpc katmai_defconfig
powerpc mpc834x_mds_defconfig
arc nsimosci_defconfig
powerpc mpc8540_ads_defconfig
mips maltaup_xpa_defconfig
arm multi_v4t_defconfig
um defconfig
powerpc mpc834x_itxgp_defconfig
powerpc mpc8313_rdb_defconfig
arm milbeaut_m10v_defconfig
arm tegra_defconfig
s390 debug_defconfig
powerpc ebony_defconfig
powerpc holly_defconfig
x86_64 allnoconfig
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
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
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
i386 randconfig-a001-20210622
i386 randconfig-a002-20210622
i386 randconfig-a003-20210622
i386 randconfig-a006-20210622
i386 randconfig-a005-20210622
i386 randconfig-a004-20210622
x86_64 randconfig-a012-20210622
x86_64 randconfig-a016-20210622
x86_64 randconfig-a015-20210622
x86_64 randconfig-a014-20210622
x86_64 randconfig-a013-20210622
x86_64 randconfig-a011-20210622
i386 randconfig-a011-20210622
i386 randconfig-a014-20210622
i386 randconfig-a013-20210622
i386 randconfig-a015-20210622
i386 randconfig-a016-20210622
i386 randconfig-a012-20210622
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
um kunit_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-b001-20210622
x86_64 randconfig-a002-20210622
x86_64 randconfig-a001-20210622
x86_64 randconfig-a005-20210622
x86_64 randconfig-a003-20210622
x86_64 randconfig-a004-20210622
x86_64 randconfig-a006-20210622
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-06-25 3: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=60d55271.LB04gQHcrMrth91n%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