From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [powerpc:fixes-test] BUILD SUCCESS f81787ef053051bef07cc879d609a624dc9b2d48
Date: Mon, 15 Mar 2021 07:02:09 +0800 [thread overview]
Message-ID: <604e95f1.YS2c8RczgK2PI/uV%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git fixes-test
branch HEAD: f81787ef053051bef07cc879d609a624dc9b2d48 powerpc: Force inlining of cpu_has_feature() to avoid build failure
elapsed time: 726m
configs tested: 111
configs skipped: 25
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 se7705_defconfig
powerpc bluestone_defconfig
sh rsk7264_defconfig
xtensa common_defconfig
sh se7722_defconfig
arc nsimosci_hs_smp_defconfig
powerpc cm5200_defconfig
h8300 alldefconfig
mips maltaaprp_defconfig
sh j2_defconfig
mips omega2p_defconfig
arm orion5x_defconfig
arm jornada720_defconfig
sh titan_defconfig
m68k sun3x_defconfig
mips jmr3927_defconfig
sh ecovec24_defconfig
nios2 alldefconfig
arm bcm2835_defconfig
mips pic32mzda_defconfig
powerpc pseries_defconfig
sh se7343_defconfig
sh sh7710voipgw_defconfig
riscv nommu_virt_defconfig
powerpc ppc6xx_defconfig
powerpc taishan_defconfig
powerpc kmeter1_defconfig
mips cavium_octeon_defconfig
powerpc mpc832x_rdb_defconfig
x86_64 alldefconfig
arm milbeaut_m10v_defconfig
xtensa defconfig
sh se7619_defconfig
parisc defconfig
openrisc defconfig
powerpc storcenter_defconfig
csky defconfig
microblaze mmu_defconfig
mips ip22_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 tinyconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20210314
i386 randconfig-a005-20210314
i386 randconfig-a003-20210314
i386 randconfig-a002-20210314
i386 randconfig-a004-20210314
i386 randconfig-a006-20210314
x86_64 randconfig-a011-20210314
x86_64 randconfig-a016-20210314
x86_64 randconfig-a013-20210314
x86_64 randconfig-a015-20210314
x86_64 randconfig-a014-20210314
x86_64 randconfig-a012-20210314
i386 randconfig-a013-20210314
i386 randconfig-a016-20210314
i386 randconfig-a011-20210314
i386 randconfig-a012-20210314
i386 randconfig-a014-20210314
i386 randconfig-a015-20210314
riscv nommu_k210_defconfig
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a006-20210314
x86_64 randconfig-a001-20210314
x86_64 randconfig-a005-20210314
x86_64 randconfig-a004-20210314
x86_64 randconfig-a002-20210314
x86_64 randconfig-a003-20210314
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-03-14 23:03 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=604e95f1.YS2c8RczgK2PI/uV%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).