From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/entry] BUILD SUCCESS bb998361999e79bc87dae1ebe0f5bf317f632585
Date: Fri, 26 Jan 2024 08:53:04 +0800 [thread overview]
Message-ID: <202401260802.Pvmrh0xe-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/entry
branch HEAD: bb998361999e79bc87dae1ebe0f5bf317f632585 x86/entry: Avoid redundant CR3 write on paranoid returns
elapsed time: 1799m
configs tested: 33
configs skipped: 132
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20240125 gcc
i386 buildonly-randconfig-002-20240125 gcc
i386 buildonly-randconfig-003-20240125 gcc
i386 buildonly-randconfig-004-20240125 gcc
i386 buildonly-randconfig-005-20240125 gcc
i386 buildonly-randconfig-006-20240125 gcc
i386 defconfig gcc
i386 randconfig-001-20240125 gcc
i386 randconfig-002-20240125 gcc
i386 randconfig-003-20240125 gcc
i386 randconfig-004-20240125 gcc
i386 randconfig-005-20240125 gcc
i386 randconfig-006-20240125 gcc
i386 randconfig-011-20240125 clang
i386 randconfig-012-20240125 clang
i386 randconfig-013-20240125 clang
i386 randconfig-014-20240125 clang
i386 randconfig-015-20240125 clang
i386 randconfig-016-20240125 clang
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20240126 clang
x86_64 buildonly-randconfig-002-20240126 clang
x86_64 buildonly-randconfig-003-20240126 clang
x86_64 buildonly-randconfig-004-20240126 clang
x86_64 buildonly-randconfig-005-20240126 clang
x86_64 buildonly-randconfig-006-20240126 clang
x86_64 defconfig gcc
x86_64 randconfig-001-20240126 gcc
x86_64 rhel-8.3-rust clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-26 0: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=202401260802.Pvmrh0xe-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.