From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>
Subject: [rdma:wip/jgg-for-next] BUILD SUCCESS 60da2d11fcbc043304910e4d2ca82f9bab953e63
Date: Wed, 16 Nov 2022 18:11:10 +0800 [thread overview]
Message-ID: <6374b73e.kWUADkNP7WScCV8H%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git wip/jgg-for-next
branch HEAD: 60da2d11fcbc043304910e4d2ca82f9bab953e63 RDMA/siw: Set defined status for work completion with undefined status
elapsed time: 725m
configs tested: 78
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
um i386_defconfig
um x86_64_defconfig
s390 allmodconfig
s390 defconfig
powerpc allmodconfig
m68k allmodconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
alpha allyesconfig
arc allyesconfig
x86_64 rhel-8.3-syz
x86_64 randconfig-a002
x86_64 rhel-8.3-kunit
arc randconfig-r043-20221115
m68k allyesconfig
x86_64 rhel-8.3-kvm
s390 randconfig-r044-20221115
ia64 allmodconfig
x86_64 defconfig
x86_64 randconfig-a006
riscv randconfig-r042-20221115
x86_64 rhel-8.3
x86_64 randconfig-a004
x86_64 allyesconfig
i386 randconfig-a001
i386 randconfig-a003
i386 defconfig
i386 randconfig-a005
i386 randconfig-a014
i386 randconfig-a012
arm defconfig
i386 randconfig-a016
arm64 allyesconfig
arm allyesconfig
i386 allyesconfig
s390 allyesconfig
powerpc allnoconfig
x86_64 allnoconfig
mips allyesconfig
sh allmodconfig
i386 randconfig-a002-20221114
i386 randconfig-a004-20221114
i386 randconfig-a003-20221114
i386 randconfig-a005-20221114
i386 randconfig-a006-20221114
i386 randconfig-a001-20221114
mips decstation_defconfig
arm footbridge_defconfig
sh apsh4a3a_defconfig
openrisc simple_smp_defconfig
m68k q40_defconfig
sparc sparc32_defconfig
powerpc makalu_defconfig
xtensa nommu_kc705_defconfig
arm pxa910_defconfig
sh rsk7264_defconfig
loongarch alldefconfig
sh sh7770_generic_defconfig
mips ip32_defconfig
clang tested configs:
x86_64 randconfig-a012-20221114
x86_64 randconfig-a016-20221114
x86_64 randconfig-a015-20221114
x86_64 randconfig-a013-20221114
x86_64 randconfig-a011-20221114
x86_64 randconfig-a014-20221114
hexagon randconfig-r041-20221115
hexagon randconfig-r045-20221115
x86_64 randconfig-a005
x86_64 randconfig-a001
x86_64 randconfig-a003
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
i386 randconfig-a006
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-11-16 10:13 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=6374b73e.kWUADkNP7WScCV8H%lkp@intel.com \
--to=lkp@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.