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 1df8f9137669ca06141f13e591960c0b860a7b06
Date: Wed, 01 Dec 2021 21:12:54 +0800 [thread overview]
Message-ID: <61a774d6.SZPS7xvXxFJpT/uP%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 1df8f9137669ca06141f13e591960c0b860a7b06 Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc
elapsed time: 912m
configs tested: 104
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm allyesconfig
arm allmodconfig
arm64 defconfig
arm64 allyesconfig
i386 randconfig-c001-20211128
mips loongson1b_defconfig
ia64 tiger_defconfig
arm badge4_defconfig
sh sh2007_defconfig
mips workpad_defconfig
arc vdk_hs38_defconfig
arm bcm2835_defconfig
mips maltaup_xpa_defconfig
sh shmin_defconfig
arm randconfig-c002-20211129
ia64 allmodconfig
ia64 allyesconfig
ia64 defconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 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 defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
mips allmodconfig
mips allyesconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a001-20211129
i386 randconfig-a002-20211129
i386 randconfig-a003-20211129
i386 randconfig-a004-20211129
i386 randconfig-a006-20211129
i386 randconfig-a005-20211129
i386 randconfig-a001-20211201
i386 randconfig-a005-20211201
i386 randconfig-a003-20211201
i386 randconfig-a002-20211201
i386 randconfig-a006-20211201
i386 randconfig-a004-20211201
x86_64 randconfig-a011-20211128
x86_64 randconfig-a012-20211128
x86_64 randconfig-a013-20211128
x86_64 randconfig-a014-20211128
x86_64 randconfig-a016-20211128
x86_64 randconfig-a015-20211128
i386 randconfig-a013-20211128
i386 randconfig-a012-20211128
i386 randconfig-a011-20211128
i386 randconfig-a015-20211128
i386 randconfig-a016-20211128
i386 randconfig-a014-20211128
arc randconfig-r043-20211128
s390 randconfig-r044-20211128
riscv randconfig-r042-20211128
riscv nommu_k210_defconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
riscv allyesconfig
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-func
x86_64 kexec
clang tested configs:
i386 randconfig-a001-20211128
i386 randconfig-a002-20211128
i386 randconfig-a006-20211128
i386 randconfig-a005-20211128
i386 randconfig-a004-20211128
i386 randconfig-a003-20211128
x86_64 randconfig-a001-20211128
x86_64 randconfig-a003-20211128
x86_64 randconfig-a004-20211128
x86_64 randconfig-a002-20211128
x86_64 randconfig-a005-20211128
x86_64 randconfig-a006-20211128
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-01 13:13 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=61a774d6.SZPS7xvXxFJpT/uP%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