From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/apic] BUILD SUCCESS f96fb2df3eb31ede1b34b0521560967310267750
Date: Sat, 08 Apr 2023 09:29:41 +0800 [thread overview]
Message-ID: <6430c385.Ax68KqFIjZcMFEEg%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/apic
branch HEAD: f96fb2df3eb31ede1b34b0521560967310267750 x86/apic: Fix atomic update of offset in reserve_eilvt_offset()
elapsed time: 722m
configs tested: 77
configs skipped: 107
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha randconfig-r005-20230403 gcc
arc randconfig-r001-20230405 gcc
arc randconfig-r002-20230403 gcc
arc randconfig-r016-20230403 gcc
arc randconfig-r043-20230403 gcc
arm randconfig-r005-20230405 gcc
arm randconfig-r021-20230403 clang
arm64 randconfig-r015-20230403 gcc
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-a001-20230403 clang
i386 randconfig-a002-20230403 clang
i386 randconfig-a003-20230403 clang
i386 randconfig-a004-20230403 clang
i386 randconfig-a005-20230403 clang
i386 randconfig-a006-20230403 clang
i386 randconfig-a011-20230403 gcc
i386 randconfig-a012-20230403 gcc
i386 randconfig-a013-20230403 gcc
i386 randconfig-a014-20230403 gcc
i386 randconfig-a015-20230403 gcc
i386 randconfig-a016-20230403 gcc
i386 randconfig-r021-20230403 gcc
i386 randconfig-r023-20230403 gcc
loongarch randconfig-r006-20230403 gcc
loongarch randconfig-r013-20230403 gcc
m68k randconfig-r001-20230403 gcc
m68k randconfig-r012-20230403 gcc
mips randconfig-r002-20230405 gcc
mips randconfig-r024-20230403 clang
mips randconfig-r026-20230403 clang
nios2 defconfig gcc
nios2 randconfig-r014-20230403 gcc
openrisc buildonly-randconfig-r001-20230403 gcc
openrisc randconfig-r011-20230403 gcc
parisc defconfig gcc
parisc randconfig-r003-20230405 gcc
parisc64 defconfig gcc
powerpc buildonly-randconfig-r004-20230403 gcc
powerpc randconfig-r013-20230403 gcc
riscv randconfig-r042-20230403 gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-r044-20230403 gcc
sh allmodconfig gcc
sparc buildonly-randconfig-r002-20230403 gcc
sparc64 buildonly-randconfig-r006-20230403 gcc
sparc64 randconfig-r014-20230403 gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a001-20230403 clang
x86_64 randconfig-a002-20230403 clang
x86_64 randconfig-a003-20230403 clang
x86_64 randconfig-a004-20230403 clang
x86_64 randconfig-a005-20230403 clang
x86_64 randconfig-a006-20230403 clang
x86_64 randconfig-a011-20230403 gcc
x86_64 randconfig-a011 gcc
x86_64 randconfig-a012-20230403 gcc
x86_64 randconfig-a013-20230403 gcc
x86_64 randconfig-a013 gcc
x86_64 randconfig-a014-20230403 gcc
x86_64 randconfig-a015-20230403 gcc
x86_64 randconfig-a015 gcc
x86_64 randconfig-a016-20230403 gcc
x86_64 randconfig-k001-20230403 gcc
x86_64 randconfig-r031-20230403 clang
x86_64 rhel-8.3-bpf gcc
x86_64 rhel-8.3-kunit gcc
x86_64 rhel-8.3-kvm gcc
x86_64 rhel-8.3-syz gcc
x86_64 rhel-8.3 gcc
xtensa buildonly-randconfig-r005-20230403 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-08 1:30 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=6430c385.Ax68KqFIjZcMFEEg%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
all inboxes | Powered by JetHome®