From: kernel test robot <lkp@intel.com>
To: David Hildenbrand <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
mm-commits@vger.kernel.org
Subject: [akpm-mm:mm-new] BUILD SUCCESS 178b3d97bf1f15f598ea7cc615a40c115e528e1c
Date: Thu, 03 Sep 2026 02:53:11 +0800 [thread overview]
Message-ID: <202609030205.mM0yURLh-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
branch HEAD: 178b3d97bf1f15f598ea7cc615a40c115e528e1c mm/swap, PM: hibernate: atomically replace hibernation pin
elapsed time: 896m
configs tested: 74
configs skipped: 0
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allnoconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
arc randconfig-r072-20260902 gcc-10.5.0
arm allnoconfig clang-17
arm allyesconfig gcc-16.1.0
arm64 allmodconfig clang-24
arm64 allnoconfig gcc-16.1.0
arm64 randconfig-r112-20260902 clang-24
csky allmodconfig gcc-16.1.0
csky allnoconfig gcc-16.1.0
hexagon allmodconfig clang-24
hexagon allnoconfig clang-24
i386 allmodconfig gcc-14
i386 allnoconfig gcc-14
i386 allyesconfig gcc-14
i386 randconfig-061-20260902 clang-22
i386 randconfig-062-20260902 gcc-14
i386 randconfig-063-20260902 gcc-14
i386 randconfig-141-20260902 clang-22
loongarch allmodconfig clang-19
loongarch allnoconfig clang-20
m68k allmodconfig gcc-16.1.0
m68k allnoconfig gcc-16.1.0
m68k allyesconfig gcc-16.1.0
m68k randconfig-r052-20260902 gcc-16.1.0
microblaze allnoconfig gcc-16.1.0
microblaze allyesconfig gcc-16.1.0
microblaze randconfig-r071-20260902 gcc-12.5.0
microblaze randconfig-r111-20260902 gcc-11.5.0
microblaze randconfig-r113-20260902 gcc-11.5.0
mips allmodconfig gcc-16.1.0
mips allnoconfig gcc-16.1.0
mips allyesconfig gcc-16.1.0
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-r054-20260902 gcc-11.5.0
openrisc allmodconfig gcc-16.1.0
openrisc allnoconfig gcc-16.1.0
parisc allmodconfig gcc-16.1.0
parisc allnoconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc randconfig-r121-20260902 gcc-9.5.0
powerpc allmodconfig gcc-16.1.0
powerpc allnoconfig gcc-16.1.0
riscv allmodconfig clang-24
riscv allnoconfig gcc-16.1.0
riscv allyesconfig clang-24
s390 allmodconfig clang-24
s390 allnoconfig clang-24
s390 allyesconfig gcc-16.1.0
sh allmodconfig gcc-16.1.0
sh allnoconfig gcc-16.1.0
sh allyesconfig gcc-16.1.0
sparc allnoconfig gcc-16.1.0
sparc64 allmodconfig clang-20
um allmodconfig clang-17
um allnoconfig clang-17
um allyesconfig gcc-14
um randconfig-r051-20260902 gcc-12
x86_64 allmodconfig clang-22
x86_64 allnoconfig clang-22
x86_64 allyesconfig clang-22
x86_64 randconfig-121-20260902 clang-22
x86_64 randconfig-122-20260902 clang-22
x86_64 randconfig-123-20260902 clang-22
x86_64 randconfig-161-20260902 clang-22
x86_64 randconfig-r122-20260902 gcc-14
x86_64 rhel-9.4-rust clang-22
xtensa allnoconfig gcc-16.1.0
xtensa allyesconfig gcc-16.1.0
xtensa randconfig-r123-20260902 gcc-8.5.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-02 18:53 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=202609030205.mM0yURLh-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.