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 077e992aebce48374837748fb608d714c61211d1
Date: Wed, 16 Dec 2020 19:18:12 +0800 [thread overview]
Message-ID: <5fd9ecf4.cfLqtTuVWrL/sUnC%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 077e992aebce48374837748fb608d714c61211d1 Merge remote-tracking branch 'btrfs-fixes/next-fixes'
elapsed time: 724m
configs tested: 110
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
arm efm32_defconfig
powerpc mpc885_ads_defconfig
powerpc mpc834x_itxgp_defconfig
arc tb10x_defconfig
powerpc ksi8560_defconfig
c6x evmc6457_defconfig
powerpc allyesconfig
powerpc fsp2_defconfig
h8300 h8300h-sim_defconfig
xtensa common_defconfig
xtensa xip_kc705_defconfig
sh se7724_defconfig
arm lart_defconfig
um i386_defconfig
ia64 bigsur_defconfig
powerpc mpc85xx_cds_defconfig
i386 alldefconfig
arm ebsa110_defconfig
powerpc pq2fads_defconfig
mips omega2p_defconfig
arm footbridge_defconfig
mips ci20_defconfig
sh se7722_defconfig
mips loongson1c_defconfig
m68k allmodconfig
m68k bvme6000_defconfig
arm versatile_defconfig
arm pxa910_defconfig
arm corgi_defconfig
mips db1xxx_defconfig
m68k m5275evb_defconfig
sh sh7757lcr_defconfig
m68k m5407c3_defconfig
sh j2_defconfig
parisc generic-32bit_defconfig
alpha allyesconfig
mips tb0226_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
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
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a003-20201215
x86_64 randconfig-a006-20201215
x86_64 randconfig-a002-20201215
x86_64 randconfig-a005-20201215
x86_64 randconfig-a004-20201215
x86_64 randconfig-a001-20201215
i386 randconfig-a001-20201215
i386 randconfig-a004-20201215
i386 randconfig-a003-20201215
i386 randconfig-a002-20201215
i386 randconfig-a006-20201215
i386 randconfig-a005-20201215
i386 randconfig-a014-20201215
i386 randconfig-a013-20201215
i386 randconfig-a012-20201215
i386 randconfig-a011-20201215
i386 randconfig-a015-20201215
i386 randconfig-a016-20201215
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 kexec
x86_64 rhel-8.3-kbuiltin
clang tested configs:
x86_64 randconfig-a016-20201215
x86_64 randconfig-a012-20201215
x86_64 randconfig-a013-20201215
x86_64 randconfig-a015-20201215
x86_64 randconfig-a014-20201215
x86_64 randconfig-a011-20201215
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-12-16 11:18 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=5fd9ecf4.cfLqtTuVWrL/sUnC%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