From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:master] BUILD SUCCESS 0f0be91c3f9ea49da23d6c47e9f3634b05b8e77c
Date: Sun, 19 Dec 2021 15:56:14 +0800 [thread overview]
Message-ID: <61bee59e.pFsN1abBNMfooINm%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
branch HEAD: 0f0be91c3f9ea49da23d6c47e9f3634b05b8e77c Merge branch 'irq/msi'
elapsed time: 725m
configs tested: 107
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
arm defconfig
mips workpad_defconfig
arm at91_dt_defconfig
powerpc lite5200b_defconfig
arc hsdk_defconfig
arm u8500_defconfig
sh sh7710voipgw_defconfig
powerpc sam440ep_defconfig
nios2 alldefconfig
powerpc ebony_defconfig
mips malta_kvm_defconfig
arm sama5_defconfig
riscv rv32_defconfig
powerpc powernv_defconfig
um x86_64_defconfig
mips jmr3927_defconfig
powerpc stx_gp3_defconfig
sh sh7785lcr_32bit_defconfig
arm shannon_defconfig
powerpc ge_imp3a_defconfig
mips ar7_defconfig
sh sh7785lcr_defconfig
arm davinci_all_defconfig
arm lubbock_defconfig
arm mainstone_defconfig
powerpc mpc834x_mds_defconfig
arm randconfig-c002-20211219
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k defconfig
m68k allyesconfig
m68k allmodconfig
nds32 defconfig
csky defconfig
alpha defconfig
alpha allyesconfig
nios2 allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
nds32 allnoconfig
nios2 defconfig
arc allyesconfig
parisc defconfig
s390 allmodconfig
s390 defconfig
parisc allyesconfig
s390 allyesconfig
i386 allyesconfig
i386 defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
sparc defconfig
sparc allyesconfig
mips allyesconfig
mips allmodconfig
powerpc allnoconfig
powerpc allmodconfig
powerpc allyesconfig
x86_64 randconfig-a011-20211219
x86_64 randconfig-a013-20211219
x86_64 randconfig-a012-20211219
x86_64 randconfig-a014-20211219
x86_64 randconfig-a015-20211219
x86_64 randconfig-a016-20211219
i386 randconfig-a013-20211219
i386 randconfig-a011-20211219
i386 randconfig-a016-20211219
i386 randconfig-a015-20211219
i386 randconfig-a014-20211219
i386 randconfig-a012-20211219
arc randconfig-r043-20211219
riscv randconfig-r042-20211219
s390 randconfig-r044-20211219
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-func
x86_64 kexec
x86_64 rhel-8.3-kselftests
clang tested configs:
x86_64 randconfig-a001-20211219
x86_64 randconfig-a003-20211219
x86_64 randconfig-a002-20211219
x86_64 randconfig-a004-20211219
x86_64 randconfig-a006-20211219
x86_64 randconfig-a005-20211219
i386 randconfig-a002-20211219
i386 randconfig-a001-20211219
i386 randconfig-a005-20211219
i386 randconfig-a003-20211219
i386 randconfig-a006-20211219
i386 randconfig-a004-20211219
hexagon randconfig-r045-20211219
hexagon randconfig-r041-20211219
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-19 7:56 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=61bee59e.pFsN1abBNMfooINm%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