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 abe70ee4912bda1466e67ba689712bc529e8114b
Date: Tue, 19 Jan 2021 05:43:00 +0800 [thread overview]
Message-ID: <600600e4.wwlBauXU6J3wnctS%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git master
branch HEAD: abe70ee4912bda1466e67ba689712bc529e8114b Merge tag 'v5.11-rc4'
elapsed time: 721m
configs tested: 110
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 allyesconfig
arm64 defconfig
arm defconfig
arm allyesconfig
arm allmodconfig
xtensa generic_kc705_defconfig
m68k alldefconfig
sh se7712_defconfig
m68k bvme6000_defconfig
m68k multi_defconfig
powerpc mpc836x_mds_defconfig
sh sh7763rdp_defconfig
xtensa virt_defconfig
m68k m5307c3_defconfig
arm h3600_defconfig
powerpc mpc8560_ads_defconfig
xtensa nommu_kc705_defconfig
powerpc mpc85xx_cds_defconfig
powerpc mpc885_ads_defconfig
powerpc mpc832x_rdb_defconfig
mips bmips_stb_defconfig
powerpc mpc834x_itx_defconfig
mips jmr3927_defconfig
arc tb10x_defconfig
powerpc motionpro_defconfig
arm at91_dt_defconfig
c6x defconfig
arm hisi_defconfig
mips bmips_be_defconfig
arm colibri_pxa300_defconfig
powerpc redwood_defconfig
m68k hp300_defconfig
sh landisk_defconfig
mips jazz_defconfig
powerpc ppc40x_defconfig
powerpc mpc7448_hpc2_defconfig
sh dreamcast_defconfig
arm axm55xx_defconfig
powerpc tqm8560_defconfig
sparc64 defconfig
arm ep93xx_defconfig
mips nlm_xlr_defconfig
powerpc cell_defconfig
mips workpad_defconfig
powerpc amigaone_defconfig
sh apsh4a3a_defconfig
mips ip32_defconfig
microblaze mmu_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
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 tinyconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a015-20210118
x86_64 randconfig-a016-20210118
x86_64 randconfig-a014-20210118
i386 randconfig-a011-20210118
i386 randconfig-a012-20210118
i386 randconfig-a016-20210118
i386 randconfig-a015-20210118
i386 randconfig-a013-20210118
i386 randconfig-a014-20210118
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 rhel-7.6-kselftests
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
x86_64 allyesconfig
x86_64 defconfig
clang tested configs:
x86_64 randconfig-a004-20210118
x86_64 randconfig-a006-20210118
x86_64 randconfig-a001-20210118
x86_64 randconfig-a003-20210118
x86_64 randconfig-a005-20210118
x86_64 randconfig-a002-20210118
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-01-18 21:44 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=600600e4.wwlBauXU6J3wnctS%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;
as well as URLs for NNTP newsgroup(s).