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 a19dc7366c4946a690e8df7cb918f2d8d0ddb8ec
Date: Wed, 15 Jun 2022 20:08:04 +0800 [thread overview]
Message-ID: <62a9cba4.vri5PbZbseGSZ84J%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: a19dc7366c4946a690e8df7cb918f2d8d0ddb8ec Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc
elapsed time: 725m
configs tested: 60
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 defconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
arm allmodconfig
ia64 defconfig
ia64 allmodconfig
ia64 allyesconfig
m68k allyesconfig
m68k allmodconfig
m68k defconfig
nios2 defconfig
arc allyesconfig
csky defconfig
nios2 allyesconfig
alpha defconfig
alpha allyesconfig
h8300 allyesconfig
xtensa allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allmodconfig
parisc allyesconfig
parisc64 defconfig
s390 defconfig
s390 allyesconfig
sparc allyesconfig
i386 allyesconfig
sparc defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
i386 defconfig
mips allmodconfig
mips allyesconfig
powerpc allyesconfig
powerpc allnoconfig
powerpc allmodconfig
arc randconfig-r043-20220613
riscv randconfig-r042-20220613
s390 randconfig-r044-20220613
riscv allnoconfig
riscv allyesconfig
riscv allmodconfig
riscv nommu_k210_defconfig
riscv rv32_defconfig
riscv nommu_virt_defconfig
riscv defconfig
um i386_defconfig
um x86_64_defconfig
x86_64 defconfig
x86_64 allyesconfig
x86_64 kexec
x86_64 rhel-8.3
x86_64 rhel-8.3-func
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-kunit
clang tested configs:
hexagon randconfig-r041-20220613
hexagon randconfig-r045-20220613
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-15 12:08 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=62a9cba4.vri5PbZbseGSZ84J%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