From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: [m68k:master] BUILD SUCCESS 95a01298967383a5c2f0ce48d6541ed9ecf40e85
Date: Tue, 27 Oct 2020 08:27:49 +0800 [thread overview]
Message-ID: <5f976985.kQVHi6UtpUpFeZJX%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git master
branch HEAD: 95a01298967383a5c2f0ce48d6541ed9ecf40e85 Merge tag 'v5.10-rc1'
elapsed time: 724m
configs tested: 109
configs skipped: 2
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
h8300 h8s-sim_defconfig
csky defconfig
x86_64 defconfig
mips nlm_xlr_defconfig
riscv rv32_defconfig
sh se7705_defconfig
arm spear6xx_defconfig
arm zx_defconfig
mips malta_defconfig
arm mv78xx0_defconfig
nios2 defconfig
mips tb0287_defconfig
mips db1xxx_defconfig
mips bmips_be_defconfig
h8300 h8300h-sim_defconfig
powerpc pmac32_defconfig
sh rts7751r2d1_defconfig
mips malta_kvm_defconfig
arm assabet_defconfig
arc alldefconfig
sh se7343_defconfig
nios2 alldefconfig
arm lart_defconfig
mips e55_defconfig
microblaze defconfig
arc axs103_defconfig
xtensa generic_kc705_defconfig
sh sh7724_generic_defconfig
powerpc linkstation_defconfig
arm collie_defconfig
sh r7780mp_defconfig
m68k m5407c3_defconfig
riscv alldefconfig
xtensa iss_defconfig
mips ip22_defconfig
sh edosk7705_defconfig
arm cm_x300_defconfig
powerpc rainier_defconfig
powerpc pseries_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a002-20201026
i386 randconfig-a003-20201026
i386 randconfig-a005-20201026
i386 randconfig-a001-20201026
i386 randconfig-a006-20201026
i386 randconfig-a004-20201026
x86_64 randconfig-a011-20201026
x86_64 randconfig-a013-20201026
x86_64 randconfig-a016-20201026
x86_64 randconfig-a015-20201026
x86_64 randconfig-a012-20201026
x86_64 randconfig-a014-20201026
i386 randconfig-a016-20201026
i386 randconfig-a015-20201026
i386 randconfig-a014-20201026
i386 randconfig-a012-20201026
i386 randconfig-a013-20201026
i386 randconfig-a011-20201026
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a001-20201026
x86_64 randconfig-a003-20201026
x86_64 randconfig-a002-20201026
x86_64 randconfig-a006-20201026
x86_64 randconfig-a004-20201026
x86_64 randconfig-a005-20201026
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-10-27 0: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=5f976985.kQVHi6UtpUpFeZJX%lkp@intel.com \
--to=lkp@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
/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