From: kbuild test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: [m68k:master] BUILD SUCCESS 3ca9dbc825eacce4fea44e6850ebb8c53e672d5b
Date: Tue, 14 Jan 2020 13:12:09 +0800 [thread overview]
Message-ID: <5e1d4da9.rasPx/nmglHUJYXg%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git master
branch HEAD: 3ca9dbc825eacce4fea44e6850ebb8c53e672d5b m68k: Wire up clone3() syscall
elapsed time: 2008m
configs tested: 112
The following configs have been built successfully.
More configs may be tested in the coming days.
x86_64 fedora-25
x86_64 kexec
x86_64 lkp
x86_64 rhel
x86_64 rhel-7.6
mips 32r2_defconfig
mips 64r6el_defconfig
mips allmodconfig
mips allnoconfig
mips allyesconfig
mips fuloong2e_defconfig
mips malta_kvm_defconfig
i386 randconfig-a003-20200112
x86_64 randconfig-a002-20200112
x86_64 randconfig-a001-20200112
i386 randconfig-a002-20200112
i386 randconfig-a001-20200112
x86_64 randconfig-a003-20200112
s390 alldefconfig
s390 allmodconfig
s390 allnoconfig
s390 allyesconfig
s390 debug_defconfig
s390 defconfig
s390 zfcpdump_defconfig
i386 allnoconfig
i386 defconfig
i386 allyesconfig
i386 alldefconfig
c6x allyesconfig
c6x evmc6678_defconfig
nios2 10m50_defconfig
nios2 3c120_defconfig
openrisc or1ksim_defconfig
openrisc simple_smp_defconfig
xtensa common_defconfig
xtensa iss_defconfig
h8300 edosk2674_defconfig
h8300 h8300h-sim_defconfig
h8300 h8s-sim_defconfig
m68k allmodconfig
m68k m5475evb_defconfig
m68k multi_defconfig
m68k sun3_defconfig
arm allmodconfig
arm allnoconfig
arm allyesconfig
arm at91_dt_defconfig
arm efm32_defconfig
arm exynos_defconfig
arm multi_v5_defconfig
arm multi_v7_defconfig
arm shmobile_defconfig
arm sunxi_defconfig
arm64 allmodconfig
arm64 allnoconfig
arm64 allyesconfig
arm64 defconfig
ia64 allmodconfig
ia64 allnoconfig
ia64 allyesconfig
ia64 defconfig
ia64 alldefconfig
alpha defconfig
csky defconfig
nds32 allnoconfig
nds32 defconfig
mips randconfig-a001-20200112
riscv randconfig-a001-20200112
parisc randconfig-a001-20200112
alpha randconfig-a001-20200112
m68k randconfig-a001-20200112
nds32 randconfig-a001-20200112
sparc64 allmodconfig
sparc allyesconfig
sparc64 allyesconfig
sparc defconfig
sparc64 allnoconfig
sparc64 defconfig
riscv allmodconfig
riscv allnoconfig
riscv allyesconfig
riscv defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
parisc allnoconfig
parisc allyesonfig
parisc b180_defconfig
parisc c3000_defconfig
parisc defconfig
arc allyesconfig
arc defconfig
microblaze mmu_defconfig
microblaze nommu_defconfig
powerpc allnoconfig
powerpc defconfig
powerpc ppc64_defconfig
powerpc rhel-kconfig
um defconfig
um i386_defconfig
um x86_64_defconfig
arc randconfig-a001-20200112
arm randconfig-a001-20200112
arm64 randconfig-a001-20200112
ia64 randconfig-a001-20200112
powerpc randconfig-a001-20200112
sparc randconfig-a001-20200112
sh allmodconfig
sh allnoconfig
sh rsk7269_defconfig
sh sh7785lcr_32bit_defconfig
sh titan_defconfig
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
reply other threads:[~2020-01-14 5:12 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=5e1d4da9.rasPx/nmglHUJYXg%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).