From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/urgent] BUILD SUCCESS 39163d5479285a36522b6e8f9cc568cc4987db08
Date: Wed, 09 Aug 2023 03:58:03 +0800 [thread overview]
Message-ID: <202308090302.74sqedad-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: 39163d5479285a36522b6e8f9cc568cc4987db08 x86/vdso: Choose the right GDT_ENTRY_CPUNODE for 32-bit getcpu() on 64-bit kernel
elapsed time: 720m
configs tested: 35
configs skipped: 92
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
i386 allyesconfig gcc
i386 buildonly-randconfig-r004-20230808 clang
i386 buildonly-randconfig-r006-20230808 clang
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i001-20230808 clang
i386 randconfig-i002-20230808 clang
i386 randconfig-i003-20230808 clang
i386 randconfig-i004-20230808 clang
i386 randconfig-i005-20230808 clang
i386 randconfig-i006-20230808 clang
i386 randconfig-i011-20230808 gcc
i386 randconfig-i012-20230808 gcc
i386 randconfig-i013-20230808 gcc
i386 randconfig-i014-20230808 gcc
i386 randconfig-i015-20230808 gcc
i386 randconfig-i016-20230808 gcc
x86_64 allyesconfig gcc
x86_64 buildonly-randconfig-r001-20230808 clang
x86_64 buildonly-randconfig-r002-20230808 clang
x86_64 buildonly-randconfig-r003-20230808 clang
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-x001-20230808 gcc
x86_64 randconfig-x002-20230808 gcc
x86_64 randconfig-x003-20230808 gcc
x86_64 randconfig-x004-20230808 gcc
x86_64 randconfig-x005-20230808 gcc
x86_64 randconfig-x006-20230808 gcc
x86_64 randconfig-x011-20230808 clang
x86_64 randconfig-x012-20230808 clang
x86_64 randconfig-x013-20230808 clang
x86_64 randconfig-x014-20230808 clang
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-08 21:17 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=202308090302.74sqedad-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox