From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS 7aa7d4559632edf7cc109be084cf98b4b17acaa5
Date: Mon, 01 Jul 2024 01:28:24 +0800 [thread overview]
Message-ID: <202407010122.BWLeRMVS-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: 7aa7d4559632edf7cc109be084cf98b4b17acaa5 Merge branch 'for-linux-next-fixes' of https://gitlab.freedesktop.org/drm/misc/kernel.git
elapsed time: 3149m
configs tested: 66
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-13.2.0
arc allnoconfig gcc-13.2.0
arc randconfig-001-20240630 gcc-13.2.0
arc randconfig-002-20240630 gcc-13.2.0
arm allnoconfig clang-19
arm pxa910_defconfig gcc-13.2.0
arm randconfig-001-20240630 gcc-13.2.0
arm randconfig-002-20240630 clang-17
arm randconfig-003-20240630 clang-19
arm randconfig-004-20240630 clang-19
arm64 allnoconfig gcc-13.2.0
arm64 randconfig-001-20240630 clang-15
csky allnoconfig gcc-13.2.0
hexagon allnoconfig clang-19
i386 allmodconfig gcc-13
i386 allnoconfig gcc-13
i386 allyesconfig gcc-13
i386 buildonly-randconfig-001-20240629 gcc-7
i386 buildonly-randconfig-002-20240629 gcc-7
i386 buildonly-randconfig-003-20240629 gcc-7
i386 buildonly-randconfig-004-20240629 gcc-7
i386 buildonly-randconfig-005-20240629 gcc-7
i386 buildonly-randconfig-006-20240629 gcc-7
i386 defconfig clang-18
i386 randconfig-001-20240629 gcc-7
i386 randconfig-002-20240629 gcc-7
i386 randconfig-003-20240629 gcc-7
i386 randconfig-004-20240629 gcc-7
i386 randconfig-005-20240629 gcc-7
i386 randconfig-006-20240629 gcc-7
i386 randconfig-011-20240629 gcc-7
i386 randconfig-012-20240629 gcc-7
i386 randconfig-013-20240629 gcc-7
i386 randconfig-014-20240629 gcc-7
i386 randconfig-015-20240629 gcc-7
i386 randconfig-016-20240629 gcc-7
loongarch allmodconfig gcc-13.2.0
loongarch allnoconfig gcc-13.2.0
m68k allmodconfig gcc-13.2.0
m68k allnoconfig gcc-13.2.0
m68k allyesconfig gcc-13.2.0
microblaze allmodconfig gcc-13.2.0
microblaze allnoconfig gcc-13.2.0
microblaze allyesconfig gcc-13.2.0
mips allnoconfig gcc-13.2.0
nios2 allnoconfig gcc-13.2.0
openrisc allnoconfig gcc-13.2.0
parisc allnoconfig gcc-13.2.0
powerpc allnoconfig gcc-13.2.0
riscv allnoconfig gcc-13.2.0
s390 allnoconfig gcc-13.2.0
sh allnoconfig gcc-13.2.0
um allnoconfig gcc-13.2.0
x86_64 allnoconfig clang-18
x86_64 allyesconfig clang-18
x86_64 buildonly-randconfig-001-20240630 gcc-13
x86_64 buildonly-randconfig-002-20240630 gcc-11
x86_64 buildonly-randconfig-003-20240630 clang-18
x86_64 buildonly-randconfig-004-20240630 gcc-11
x86_64 buildonly-randconfig-005-20240630 clang-18
x86_64 buildonly-randconfig-006-20240630 clang-18
x86_64 defconfig gcc-13
x86_64 randconfig-001-20240630 clang-18
x86_64 randconfig-002-20240630 gcc-8
x86_64 rhel-8.3-rust clang-18
xtensa allnoconfig gcc-13.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-30 17:29 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=202407010122.BWLeRMVS-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.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