From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:locking/core] BUILD SUCCESS bd9a5fc2edb0bdcb0756298daa31ddd6a02f0634
Date: Mon, 29 Mar 2021 15:38:35 +0800 [thread overview]
Message-ID: <606183fb.ru8IcFwLg0GSvGUM%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
branch HEAD: bd9a5fc2edb0bdcb0756298daa31ddd6a02f0634 MAINTAINERS: Add myself as futex reviewer
elapsed time: 720m
configs tested: 112
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
x86_64 allyesconfig
riscv allmodconfig
i386 allyesconfig
riscv allyesconfig
arm aspeed_g4_defconfig
arm pxa_defconfig
sparc sparc32_defconfig
ia64 alldefconfig
powerpc icon_defconfig
arc nsimosci_defconfig
powerpc chrp32_defconfig
arm omap2plus_defconfig
sh rsk7264_defconfig
riscv nommu_virt_defconfig
um kunit_defconfig
mips cu1830-neo_defconfig
sh kfr2r09-romimage_defconfig
mips ip32_defconfig
sh shx3_defconfig
m68k multi_defconfig
mips workpad_defconfig
nios2 10m50_defconfig
powerpc lite5200b_defconfig
mips nlm_xlp_defconfig
powerpc mpc8313_rdb_defconfig
sh sdk7780_defconfig
powerpc mpc8560_ads_defconfig
sh r7785rp_defconfig
sh microdev_defconfig
m68k bvme6000_defconfig
sh se7705_defconfig
arm axm55xx_defconfig
powerpc xes_mpc85xx_defconfig
arm shannon_defconfig
mips loongson1b_defconfig
parisc generic-64bit_defconfig
powerpc ppc6xx_defconfig
arm ixp4xx_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
i386 tinyconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a002-20210329
x86_64 randconfig-a003-20210329
x86_64 randconfig-a006-20210329
x86_64 randconfig-a001-20210329
x86_64 randconfig-a005-20210329
x86_64 randconfig-a004-20210329
i386 randconfig-a003-20210329
i386 randconfig-a004-20210329
i386 randconfig-a001-20210329
i386 randconfig-a002-20210329
i386 randconfig-a006-20210329
i386 randconfig-a005-20210329
i386 randconfig-a014-20210328
i386 randconfig-a011-20210328
i386 randconfig-a015-20210328
i386 randconfig-a016-20210328
i386 randconfig-a013-20210328
i386 randconfig-a012-20210328
riscv nommu_k210_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a015-20210329
x86_64 randconfig-a012-20210329
x86_64 randconfig-a013-20210329
x86_64 randconfig-a014-20210329
x86_64 randconfig-a011-20210329
x86_64 randconfig-a016-20210329
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-03-29 7:40 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=606183fb.ru8IcFwLg0GSvGUM%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®