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 31c318f75dc40b05022f1eba1494878a408c100d
Date: Thu, 17 Dec 2020 23:56:50 +0800 [thread overview]
Message-ID: <5fdb7fc2.tBd4vBvwrYwEAXCB%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 31c318f75dc40b05022f1eba1494878a408c100d Merge remote-tracking branch 'btrfs-fixes/next-fixes'
elapsed time: 721m
configs tested: 113
configs skipped: 3
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
ia64 allmodconfig
c6x defconfig
mips jmr3927_defconfig
arm versatile_defconfig
arm magician_defconfig
xtensa nommu_kc705_defconfig
sh rts7751r2d1_defconfig
arm h3600_defconfig
m68k stmark2_defconfig
sh sh7757lcr_defconfig
mips cavium_octeon_defconfig
arm mainstone_defconfig
sh sh7724_generic_defconfig
arm sama5_defconfig
h8300 h8300h-sim_defconfig
arm orion5x_defconfig
mips rt305x_defconfig
powerpc pq2fads_defconfig
sh apsh4a3a_defconfig
arm keystone_defconfig
arm mv78xx0_defconfig
arm multi_v4t_defconfig
powerpc akebono_defconfig
mips fuloong2e_defconfig
powerpc cm5200_defconfig
sh apsh4ad0a_defconfig
arm ep93xx_defconfig
m68k sun3_defconfig
ia64 tiger_defconfig
arc tb10x_defconfig
xtensa common_defconfig
arm pxa168_defconfig
mips nlm_xlp_defconfig
powerpc maple_defconfig
arm s3c6400_defconfig
sh sdk7786_defconfig
powerpc ppa8548_defconfig
powerpc ppc44x_defconfig
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-a003-20201217
x86_64 randconfig-a006-20201217
x86_64 randconfig-a002-20201217
x86_64 randconfig-a005-20201217
x86_64 randconfig-a004-20201217
x86_64 randconfig-a001-20201217
i386 randconfig-a001-20201217
i386 randconfig-a004-20201217
i386 randconfig-a003-20201217
i386 randconfig-a002-20201217
i386 randconfig-a006-20201217
i386 randconfig-a005-20201217
i386 randconfig-a014-20201217
i386 randconfig-a013-20201217
i386 randconfig-a012-20201217
i386 randconfig-a011-20201217
i386 randconfig-a015-20201217
i386 randconfig-a016-20201217
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_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 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a016-20201217
x86_64 randconfig-a012-20201217
x86_64 randconfig-a013-20201217
x86_64 randconfig-a015-20201217
x86_64 randconfig-a014-20201217
x86_64 randconfig-a011-20201217
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-12-17 15:57 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=5fdb7fc2.tBd4vBvwrYwEAXCB%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