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 5933851d9e7bf62272d0212693e6b48e122a8974
Date: Wed, 24 Feb 2021 17:46:00 +0800 [thread overview]
Message-ID: <60362058.qqXPAoN37bPcEu3m%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 5933851d9e7bf62272d0212693e6b48e122a8974 Merge remote-tracking branch 'drm-misc-fixes/for-linux-next-fixes'
elapsed time: 720m
configs tested: 106
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
mips allyesconfig
arm milbeaut_m10v_defconfig
arm vexpress_defconfig
sh sh2007_defconfig
powerpc kmeter1_defconfig
arm collie_defconfig
m68k hp300_defconfig
mips ip27_defconfig
sh r7785rp_defconfig
powerpc rainier_defconfig
arm badge4_defconfig
powerpc pasemi_defconfig
sh se7751_defconfig
mips xway_defconfig
csky alldefconfig
powerpc currituck_defconfig
mips tb0226_defconfig
sh se7750_defconfig
i386 alldefconfig
sh kfr2r09-romimage_defconfig
m68k mvme16x_defconfig
sh edosk7705_defconfig
arm sama5_defconfig
arm s3c2410_defconfig
arm alldefconfig
sh lboxre2_defconfig
arm footbridge_defconfig
powerpc sequoia_defconfig
arm multi_v5_defconfig
mips ath79_defconfig
mips maltaaprp_defconfig
riscv rv32_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k 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
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 tinyconfig
i386 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20210223
i386 randconfig-a006-20210223
i386 randconfig-a004-20210223
i386 randconfig-a003-20210223
i386 randconfig-a001-20210223
i386 randconfig-a002-20210223
x86_64 randconfig-a015-20210223
x86_64 randconfig-a011-20210223
x86_64 randconfig-a012-20210223
x86_64 randconfig-a016-20210223
x86_64 randconfig-a014-20210223
x86_64 randconfig-a013-20210223
i386 randconfig-a013-20210223
i386 randconfig-a012-20210223
i386 randconfig-a011-20210223
i386 randconfig-a014-20210223
i386 randconfig-a016-20210223
i386 randconfig-a015-20210223
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
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-a001-20210223
x86_64 randconfig-a002-20210223
x86_64 randconfig-a003-20210223
x86_64 randconfig-a005-20210223
x86_64 randconfig-a006-20210223
x86_64 randconfig-a004-20210223
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-02-24 9:47 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=60362058.qqXPAoN37bPcEu3m%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