From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:locking/urgent] BUILD SUCCESS 94cd8fa09f5f1ebdd4e90964b08b7f2cc4b36c43
Date: Wed, 28 Dec 2022 08:49:02 +0800 [thread overview]
Message-ID: <63ab927e.JaRmZHkf7MV6KtVB%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/urgent
branch HEAD: 94cd8fa09f5f1ebdd4e90964b08b7f2cc4b36c43 futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error
elapsed time: 730m
configs tested: 83
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
alpha allyesconfig
arc allyesconfig
m68k allyesconfig
m68k allmodconfig
um i386_defconfig
um x86_64_defconfig
s390 defconfig
s390 allmodconfig
ia64 allmodconfig
s390 allyesconfig
powerpc allnoconfig
mips allyesconfig
powerpc allmodconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
arm defconfig
x86_64 rhel-8.3-bpf
i386 randconfig-a012-20221226
x86_64 rhel-8.3-syz
i386 randconfig-a011-20221226
x86_64 defconfig
x86_64 rhel-8.3-kunit
i386 randconfig-a013-20221226
x86_64 rhel-8.3-kvm
i386 randconfig-a014-20221226
arm64 allyesconfig
x86_64 rhel-8.3
i386 randconfig-a016-20221226
i386 defconfig
arm allyesconfig
i386 randconfig-a015-20221226
x86_64 allyesconfig
x86_64 randconfig-a014-20221226
i386 allyesconfig
x86_64 randconfig-a013-20221226
x86_64 randconfig-a011-20221226
x86_64 randconfig-a012-20221226
x86_64 randconfig-a015-20221226
x86_64 randconfig-a016-20221226
arc randconfig-r043-20221227
arm randconfig-r046-20221227
arc randconfig-r043-20221226
riscv randconfig-r042-20221226
s390 randconfig-r044-20221226
arm randconfig-r046-20221225
arc randconfig-r043-20221225
x86_64 allnoconfig
sh allmodconfig
i386 randconfig-c001
powerpc randconfig-c003-20221225
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv nommu_k210_defconfig
riscv allnoconfig
i386 debian-10.3-kselftests
i386 debian-10.3
clang tested configs:
x86_64 rhel-8.3-rust
x86_64 randconfig-a002-20221226
x86_64 randconfig-a003-20221226
x86_64 randconfig-a006-20221226
x86_64 randconfig-a001-20221226
x86_64 randconfig-a004-20221226
i386 randconfig-a004-20221226
x86_64 randconfig-a005-20221226
i386 randconfig-a001-20221226
i386 randconfig-a003-20221226
i386 randconfig-a002-20221226
i386 randconfig-a006-20221226
i386 randconfig-a005-20221226
hexagon randconfig-r041-20221227
hexagon randconfig-r041-20221226
arm randconfig-r046-20221226
hexagon randconfig-r045-20221226
hexagon randconfig-r045-20221227
riscv randconfig-r042-20221227
s390 randconfig-r044-20221227
hexagon randconfig-r045-20221225
hexagon randconfig-r041-20221225
s390 randconfig-r044-20221225
riscv randconfig-r042-20221225
x86_64 randconfig-k001
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-12-28 0:50 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=63ab927e.JaRmZHkf7MV6KtVB%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®