From: kernel test robot <lkp@intel.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org, Jason Gunthorpe <jgg+lists@ziepe.ca>,
Doug Ledford <dledford@redhat.com>
Subject: [rdma:wip/leon-for-next] BUILD SUCCESS bbdad4967431bda9424aff2295c23d48c5059941
Date: Fri, 28 Oct 2022 08:19:18 +0800 [thread overview]
Message-ID: <635b2006.58egwmY79XPOLX5L%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git wip/leon-for-next
branch HEAD: bbdad4967431bda9424aff2295c23d48c5059941 RDMA/core: Fix order of nldev_exit call
elapsed time: 723m
configs tested: 58
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
arc defconfig
x86_64 defconfig
alpha defconfig
alpha allyesconfig
arc randconfig-r043-20221027
arc allyesconfig
m68k allyesconfig
x86_64 rhel-8.3
m68k allmodconfig
x86_64 allyesconfig
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-kvm
ia64 allmodconfig
x86_64 randconfig-a013
i386 defconfig
s390 defconfig
x86_64 randconfig-a011
i386 randconfig-a001
s390 allmodconfig
x86_64 rhel-8.3-func
x86_64 randconfig-a004
x86_64 rhel-8.3-kselftests
i386 randconfig-a003
powerpc allnoconfig
x86_64 randconfig-a002
powerpc allmodconfig
i386 allyesconfig
x86_64 randconfig-a015
x86_64 randconfig-a006
mips allyesconfig
arm defconfig
sh allmodconfig
i386 randconfig-a005
i386 randconfig-a014
s390 allyesconfig
i386 randconfig-a012
i386 randconfig-a016
arm allyesconfig
arm64 allyesconfig
clang tested configs:
hexagon randconfig-r041-20221027
hexagon randconfig-r045-20221027
riscv randconfig-r042-20221027
s390 randconfig-r044-20221027
x86_64 randconfig-a012
x86_64 randconfig-a001
i386 randconfig-a002
i386 randconfig-a013
i386 randconfig-a015
x86_64 randconfig-a003
x86_64 randconfig-a005
x86_64 randconfig-a014
i386 randconfig-a006
i386 randconfig-a011
i386 randconfig-a004
x86_64 randconfig-a016
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-10-28 0:20 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=635b2006.58egwmY79XPOLX5L%lkp@intel.com \
--to=lkp@intel.com \
--cc=dledford@redhat.com \
--cc=jgg+lists@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.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