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 6f779e1d359b8d5801f677c1d49dcfa10bf95674
Date: Fri, 15 Oct 2021 10:26:01 +0800 [thread overview]
Message-ID: <6168e6b9.RvqDB+5J277M6kEu%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git fixes-test
branch HEAD: 6f779e1d359b8d5801f677c1d49dcfa10bf95674 powerpc/xive: Discard disabled interrupts in get_irqchip_state()
elapsed time: 728m
configs tested: 99
configs skipped: 94
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
i386 randconfig-c001-20211014
arm zeus_defconfig
sh se7206_defconfig
sh ap325rxa_defconfig
arm qcom_defconfig
arc axs103_smp_defconfig
powerpc currituck_defconfig
mips decstation_64_defconfig
powerpc skiroot_defconfig
mips workpad_defconfig
mips loongson2k_defconfig
arc haps_hs_smp_defconfig
m68k atari_defconfig
um defconfig
powerpc tqm8xx_defconfig
powerpc adder875_defconfig
arc nsim_700_defconfig
powerpc tqm8541_defconfig
nios2 3c120_defconfig
mips fuloong2e_defconfig
powerpc warp_defconfig
openrisc or1ksim_defconfig
powerpc ge_imp3a_defconfig
powerpc lite5200b_defconfig
powerpc sequoia_defconfig
arm randconfig-c002-20211014
x86_64 randconfig-c001-20211014
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
nds32 allnoconfig
nds32 defconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a003-20211014
i386 randconfig-a001-20211014
i386 randconfig-a005-20211014
i386 randconfig-a004-20211014
i386 randconfig-a002-20211014
i386 randconfig-a006-20211014
x86_64 randconfig-a006-20211014
x86_64 randconfig-a004-20211014
x86_64 randconfig-a001-20211014
x86_64 randconfig-a005-20211014
x86_64 randconfig-a002-20211014
x86_64 randconfig-a003-20211014
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
arm randconfig-c002-20211014
i386 randconfig-c001-20211014
s390 randconfig-c005-20211014
x86_64 randconfig-c007-20211014
powerpc randconfig-c003-20211014
riscv randconfig-c006-20211014
x86_64 randconfig-a012-20211014
x86_64 randconfig-a015-20211014
x86_64 randconfig-a016-20211014
x86_64 randconfig-a014-20211014
x86_64 randconfig-a011-20211014
x86_64 randconfig-a013-20211014
i386 randconfig-a016-20211014
i386 randconfig-a014-20211014
i386 randconfig-a011-20211014
i386 randconfig-a015-20211014
i386 randconfig-a012-20211014
i386 randconfig-a013-20211014
hexagon randconfig-r041-20211014
s390 randconfig-r044-20211014
riscv randconfig-r042-20211014
hexagon randconfig-r045-20211014
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-10-15 2:28 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=6168e6b9.RvqDB+5J277M6kEu%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