From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/microcode] BUILD SUCCESS 5b1586ab064ca24c6a7a6be7a9d0cb9e237ef39a
Date: Sun, 04 Dec 2022 10:21:52 +0800 [thread overview]
Message-ID: <638c0440.V7l07Y+GheNAksLU%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/microcode
branch HEAD: 5b1586ab064ca24c6a7a6be7a9d0cb9e237ef39a x86/microcode/intel: Do not print microcode revision and processor flags
elapsed time: 754m
configs tested: 55
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arc defconfig
alpha defconfig
s390 allmodconfig
s390 defconfig
um x86_64_defconfig
um i386_defconfig
s390 allyesconfig
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
ia64 allmodconfig
powerpc allnoconfig
m68k allyesconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
i386 randconfig-a001
alpha allyesconfig
i386 randconfig-a003
arc allyesconfig
i386 randconfig-a005
arc randconfig-r043-20221201
riscv randconfig-r042-20221201
s390 randconfig-r044-20221201
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
x86_64 randconfig-a006
x86_64 randconfig-a004
x86_64 randconfig-a002
m68k allmodconfig
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
sh allmodconfig
mips allyesconfig
powerpc allmodconfig
i386 allyesconfig
i386 defconfig
arm64 allyesconfig
arm defconfig
arm allyesconfig
x86_64 allnoconfig
clang tested configs:
i386 randconfig-a002
i386 randconfig-a004
x86_64 randconfig-a012
x86_64 randconfig-a014
x86_64 randconfig-a016
i386 randconfig-a006
x86_64 randconfig-a005
x86_64 randconfig-a003
x86_64 randconfig-a001
hexagon randconfig-r041-20221204
riscv randconfig-r042-20221204
hexagon randconfig-r045-20221204
s390 randconfig-r044-20221204
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-12-04 2:22 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=638c0440.V7l07Y+GheNAksLU%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®