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 dbc40beb5545ecb25b90451ad0e6c339b0a32ca2
Date: Thu, 04 Mar 2021 19:50:01 +0800 [thread overview]
Message-ID: <6040c969.A5PtEFfFFFgE3fcU%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: dbc40beb5545ecb25b90451ad0e6c339b0a32ca2 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 723m
configs tested: 97
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
m68k mvme16x_defconfig
arm pcm027_defconfig
arm pxa255-idp_defconfig
arm s5pv210_defconfig
xtensa alldefconfig
arm spear13xx_defconfig
mips db1xxx_defconfig
mips maltasmvp_defconfig
openrisc or1ksim_defconfig
nds32 allnoconfig
parisc allyesconfig
sh se7705_defconfig
sh rsk7203_defconfig
powerpc mpc8540_ads_defconfig
riscv defconfig
sh urquell_defconfig
arc vdk_hs38_smp_defconfig
parisc generic-32bit_defconfig
arm multi_v5_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
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-a006-20210304
x86_64 randconfig-a001-20210304
x86_64 randconfig-a004-20210304
x86_64 randconfig-a005-20210304
x86_64 randconfig-a002-20210304
x86_64 randconfig-a003-20210304
i386 randconfig-a005-20210304
i386 randconfig-a003-20210304
i386 randconfig-a002-20210304
i386 randconfig-a004-20210304
i386 randconfig-a006-20210304
i386 randconfig-a001-20210304
x86_64 randconfig-a013-20210303
x86_64 randconfig-a016-20210303
x86_64 randconfig-a015-20210303
x86_64 randconfig-a014-20210303
x86_64 randconfig-a012-20210303
x86_64 randconfig-a011-20210303
i386 randconfig-a016-20210304
i386 randconfig-a012-20210304
i386 randconfig-a013-20210304
i386 randconfig-a014-20210304
i386 randconfig-a011-20210304
i386 randconfig-a015-20210304
riscv nommu_k210_defconfig
riscv allyesconfig
riscv allnoconfig
riscv allmodconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
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-a013-20210304
x86_64 randconfig-a016-20210304
x86_64 randconfig-a015-20210304
x86_64 randconfig-a014-20210304
x86_64 randconfig-a012-20210304
x86_64 randconfig-a011-20210304
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-03-04 11:50 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=6040c969.A5PtEFfFFFgE3fcU%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