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 f4dd85cd788b42bad73ffd0ae6d3f954fb746ed6
Date: Tue, 13 Oct 2020 18:49:11 +0800 [thread overview]
Message-ID: <5f858627.4EAimU4iAB6u5HC6%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: f4dd85cd788b42bad73ffd0ae6d3f954fb746ed6 Merge remote-tracking branch 'ubifs-fixes/fixes' into master
elapsed time: 721m
configs tested: 93
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 allyesconfig
arm allyesconfig
arm allmodconfig
arm defconfig
arm64 defconfig
powerpc sam440ep_defconfig
s390 debug_defconfig
ia64 defconfig
powerpc cm5200_defconfig
arm mmp2_defconfig
sh rsk7201_defconfig
um x86_64_defconfig
nios2 allyesconfig
powerpc g5_defconfig
m68k m5272c3_defconfig
mips loongson3_defconfig
h8300 edosk2674_defconfig
powerpc pcm030_defconfig
arm64 alldefconfig
arm rpc_defconfig
powerpc tqm8555_defconfig
arm multi_v4t_defconfig
nios2 3c120_defconfig
mips ip27_defconfig
powerpc pq2fads_defconfig
mips pnx8335_stb225_defconfig
ia64 allmodconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
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 allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20201012
i386 randconfig-a006-20201012
i386 randconfig-a001-20201012
i386 randconfig-a003-20201012
i386 randconfig-a004-20201012
i386 randconfig-a002-20201012
x86_64 randconfig-a016-20201012
x86_64 randconfig-a015-20201012
x86_64 randconfig-a012-20201012
x86_64 randconfig-a013-20201012
x86_64 randconfig-a014-20201012
x86_64 randconfig-a011-20201012
i386 randconfig-a016-20201012
i386 randconfig-a015-20201012
i386 randconfig-a013-20201012
i386 randconfig-a012-20201012
i386 randconfig-a011-20201012
i386 randconfig-a014-20201012
x86_64 randconfig-a004-20201013
x86_64 randconfig-a002-20201013
x86_64 randconfig-a006-20201013
x86_64 randconfig-a001-20201013
x86_64 randconfig-a003-20201013
x86_64 randconfig-a005-20201013
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
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-10-13 10:49 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=5f858627.4EAimU4iAB6u5HC6%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