From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS 983112062f35f324bcd3fcfdaa679a7b5ce5095f
Date: Wed, 05 Aug 2020 21:08:46 +0800 [thread overview]
Message-ID: <5f2aaf5e.skHx9JRtG91mPcY7%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 983112062f35f324bcd3fcfdaa679a7b5ce5095f Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 720m
configs tested: 109
configs skipped: 9
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
mips db1xxx_defconfig
m68k amiga_defconfig
arc nsim_700_defconfig
powerpc wii_defconfig
mips ip32_defconfig
arm axm55xx_defconfig
xtensa xip_kc705_defconfig
m68k m5475evb_defconfig
powerpc holly_defconfig
sh rsk7269_defconfig
arc haps_hs_smp_defconfig
arm mini2440_defconfig
powerpc pmac32_defconfig
mips fuloong2e_defconfig
mips loongson1c_defconfig
arm lpd270_defconfig
m68k alldefconfig
arm am200epdkit_defconfig
arm nhk8815_defconfig
powerpc chrp32_defconfig
mips omega2p_defconfig
arm xcep_defconfig
sh rts7751r2dplus_defconfig
s390 debug_defconfig
powerpc powernv_defconfig
arm spear6xx_defconfig
sh apsh4a3a_defconfig
mips gpr_defconfig
arm imx_v4_v5_defconfig
arm eseries_pxa_defconfig
arm pleb_defconfig
arm keystone_defconfig
arm collie_defconfig
arm shannon_defconfig
arm davinci_all_defconfig
xtensa generic_kc705_defconfig
arm moxart_defconfig
sh sh2007_defconfig
arc vdk_hs38_defconfig
arm tct_hammer_defconfig
mips loongson1b_defconfig
powerpc ppc64_defconfig
arm ezx_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 defconfig
mips allyesconfig
mips allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20200805
i386 randconfig-a004-20200805
i386 randconfig-a001-20200805
i386 randconfig-a003-20200805
i386 randconfig-a002-20200805
i386 randconfig-a006-20200805
x86_64 randconfig-a013-20200805
x86_64 randconfig-a011-20200805
x86_64 randconfig-a012-20200805
x86_64 randconfig-a016-20200805
x86_64 randconfig-a015-20200805
x86_64 randconfig-a014-20200805
i386 randconfig-a011-20200805
i386 randconfig-a012-20200805
i386 randconfig-a013-20200805
i386 randconfig-a014-20200805
i386 randconfig-a015-20200805
i386 randconfig-a016-20200805
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-08-05 13: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=5f2aaf5e.skHx9JRtG91mPcY7%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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