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 7905dafdefe9f1238a3ca2795cf975b311b5a5f6
Date: Tue, 04 May 2021 10:49:21 +0800 [thread overview]
Message-ID: <6090b631.4yKJxsQZwWTjMpwr%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test
branch HEAD: 7905dafdefe9f1238a3ca2795cf975b311b5a5f6 powerpc/pseries: warn if recursing into the hcall tracing code
elapsed time: 2157m
configs tested: 108
configs skipped: 98
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
riscv allyesconfig
mips tb0219_defconfig
mips ip27_defconfig
sh apsh4ad0a_defconfig
riscv allnoconfig
arm neponset_defconfig
powerpc xes_mpc85xx_defconfig
powerpc warp_defconfig
xtensa defconfig
mips e55_defconfig
arm pxa_defconfig
arm clps711x_defconfig
m68k m5475evb_defconfig
mips loongson1c_defconfig
arm exynos_defconfig
sh polaris_defconfig
powerpc cm5200_defconfig
sparc64 alldefconfig
powerpc mpc7448_hpc2_defconfig
powerpc kmeter1_defconfig
arc allyesconfig
arm lart_defconfig
powerpc ep8248e_defconfig
arm multi_v5_defconfig
arm pxa910_defconfig
m68k multi_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
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-a003-20210503
i386 randconfig-a006-20210503
i386 randconfig-a001-20210503
i386 randconfig-a005-20210503
i386 randconfig-a004-20210503
i386 randconfig-a002-20210503
i386 randconfig-a003-20210502
i386 randconfig-a006-20210502
i386 randconfig-a001-20210502
i386 randconfig-a005-20210502
i386 randconfig-a004-20210502
i386 randconfig-a002-20210502
x86_64 randconfig-a014-20210502
x86_64 randconfig-a015-20210502
x86_64 randconfig-a012-20210502
x86_64 randconfig-a011-20210502
x86_64 randconfig-a013-20210502
x86_64 randconfig-a016-20210502
i386 randconfig-a013-20210502
i386 randconfig-a015-20210502
i386 randconfig-a016-20210502
i386 randconfig-a014-20210502
i386 randconfig-a011-20210502
i386 randconfig-a012-20210502
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a001-20210502
x86_64 randconfig-a005-20210502
x86_64 randconfig-a003-20210502
x86_64 randconfig-a002-20210502
x86_64 randconfig-a006-20210502
x86_64 randconfig-a004-20210502
x86_64 randconfig-a014-20210503
x86_64 randconfig-a015-20210503
x86_64 randconfig-a012-20210503
x86_64 randconfig-a011-20210503
x86_64 randconfig-a013-20210503
x86_64 randconfig-a016-20210503
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-05-04 2:50 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=6090b631.4yKJxsQZwWTjMpwr%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