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 0f88130e8a6fd185b0aeb5d8e286083735f2585a
Date: Tue, 09 May 2023 12:56:53 +0800 [thread overview]
Message-ID: <20230509045653.xrtKs%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/mm
branch HEAD: 0f88130e8a6fd185b0aeb5d8e286083735f2585a x86/mm: Fix __swp_entry_to_pte() for Xen PV guests
elapsed time: 728m
configs tested: 32
configs skipped: 123
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-a001-20230508 clang
i386 randconfig-a002-20230508 clang
i386 randconfig-a003-20230508 clang
i386 randconfig-a004-20230508 clang
i386 randconfig-a005-20230508 clang
i386 randconfig-a006-20230508 clang
i386 randconfig-a011-20230508 gcc
i386 randconfig-a012-20230508 gcc
i386 randconfig-a013-20230508 gcc
i386 randconfig-a014-20230508 gcc
i386 randconfig-a015-20230508 gcc
i386 randconfig-a016-20230508 gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a001-20230508 clang
x86_64 randconfig-a002-20230508 clang
x86_64 randconfig-a003-20230508 clang
x86_64 randconfig-a004-20230508 clang
x86_64 randconfig-a005-20230508 clang
x86_64 randconfig-a006-20230508 clang
x86_64 randconfig-a011-20230508 gcc
x86_64 randconfig-a012-20230508 gcc
x86_64 randconfig-a013-20230508 gcc
x86_64 randconfig-a014-20230508 gcc
x86_64 randconfig-a015-20230508 gcc
x86_64 randconfig-a016-20230508 gcc
x86_64 rhel-8.3 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-05-09 4:57 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=20230509045653.xrtKs%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.