From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/mm] BUILD SUCCESS dee87e09b0dd63da9b1e1876167ccae37842dfd0
Date: Sat, 15 Aug 2026 05:43:49 +0800 [thread overview]
Message-ID: <202608150537.hDY2teDn-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
branch HEAD: dee87e09b0dd63da9b1e1876167ccae37842dfd0 x86/pkeys: Fix pkey_alloc() return value when pkeys are not supported
elapsed time: 794m
configs tested: 23
configs skipped: 56
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allmodconfig gcc-14
i386 buildonly-randconfig-001-20260814 clang-22
i386 buildonly-randconfig-002-20260814 gcc-13
i386 buildonly-randconfig-003-20260814 clang-22
i386 buildonly-randconfig-004-20260814 clang-22
i386 buildonly-randconfig-005-20260814 gcc-13
i386 buildonly-randconfig-006-20260814 gcc-14
x86_64 buildonly-randconfig-002-20260815 gcc-14
x86_64 buildonly-randconfig-003-20260815 gcc-14
x86_64 buildonly-randconfig-004-20260815 gcc-14
x86_64 buildonly-randconfig-005-20260815 gcc-14
x86_64 randconfig-001-20260814 gcc-14
x86_64 randconfig-002-20260814 clang-22
x86_64 randconfig-003-20260814 clang-22
x86_64 randconfig-004-20260814 clang-22
x86_64 randconfig-005-20260814 gcc-14
x86_64 randconfig-006-20260814 gcc-14
x86_64 randconfig-011-20260814 clang-22
x86_64 randconfig-012-20260814 gcc-13
x86_64 randconfig-013-20260814 clang-22
x86_64 randconfig-014-20260814 gcc-14
x86_64 randconfig-015-20260814 gcc-14
x86_64 randconfig-016-20260814 clang-22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-14 21:44 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=202608150537.hDY2teDn-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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.