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 58bd8c0e6d69120ef25027b2de2885ca6943c6b4
Date: Wed, 17 May 2023 20:31:25 +0800 [thread overview]
Message-ID: <20230517123125.lL-_A%lkp@intel.com> (raw)
tree/branch: INFO setup_repo_specs: /db/releases/20230517200055/lkp-src/repo/*/linux-next
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 58bd8c0e6d69120ef25027b2de2885ca6943c6b4 Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc
elapsed time: 728m
configs tested: 83
configs skipped: 8
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
alpha defconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-r001-20230517 gcc
arc randconfig-r031-20230515 gcc
arc randconfig-r043-20230515 gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm randconfig-r022-20230516 gcc
arm randconfig-r046-20230515 clang
arm64 allyesconfig gcc
arm64 buildonly-randconfig-r003-20230517 clang
arm64 defconfig gcc
arm64 randconfig-r002-20230517 clang
arm64 randconfig-r006-20230517 clang
csky defconfig gcc
csky randconfig-r014-20230515 gcc
csky randconfig-r035-20230515 gcc
hexagon randconfig-r026-20230516 clang
hexagon randconfig-r041-20230515 clang
hexagon randconfig-r045-20230515 clang
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i071-20230515 gcc
i386 randconfig-i072-20230515 gcc
i386 randconfig-i073-20230515 gcc
i386 randconfig-i074-20230515 gcc
i386 randconfig-i076-20230515 gcc
ia64 allmodconfig gcc
ia64 buildonly-randconfig-r004-20230517 gcc
ia64 defconfig gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
loongarch randconfig-r023-20230516 gcc
loongarch randconfig-r034-20230515 gcc
m68k allmodconfig gcc
m68k defconfig gcc
microblaze randconfig-r013-20230515 gcc
microblaze randconfig-r021-20230516 gcc
mips allmodconfig gcc
mips allyesconfig gcc
mips randconfig-r034-20230516 clang
mips randconfig-r035-20230516 clang
nios2 defconfig gcc
nios2 randconfig-r003-20230517 gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv defconfig gcc
riscv randconfig-r042-20230515 gcc
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-r012-20230515 gcc
s390 randconfig-r032-20230515 clang
s390 randconfig-r033-20230515 clang
s390 randconfig-r044-20230515 gcc
sh allmodconfig gcc
sh randconfig-r005-20230517 gcc
sh randconfig-r024-20230516 gcc
sh randconfig-r036-20230516 gcc
sparc defconfig gcc
sparc randconfig-r015-20230515 gcc
sparc64 randconfig-r011-20230515 gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a006 gcc
x86_64 randconfig-r016-20230515 gcc
x86_64 rhel-8.3 gcc
xtensa buildonly-randconfig-r002-20230517 gcc
xtensa randconfig-r004-20230517 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-05-17 12:32 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=20230517123125.lL-_A%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