From: kernel test robot <lkp@intel.com>
To: Patrisious Haddad <phaddad@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Leon Romanovsky <leon@kernel.org>, Mark Bloch <mbloch@nvidia.com>
Subject: [leon-rdma:rdma-next 68/73] ERROR: modpost: "mlx5r_fs_bind_op_fc" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
Date: Fri, 7 Mar 2025 15:12:24 +0800 [thread overview]
Message-ID: <202503071503.PnhQY3CE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git rdma-next
head: d0ddfe3f2ff8ba858b1b9f604339bc537ef98cff
commit: 97a3fed386aa190963e63be4bf0ddc5fab34effb [68/73] RDMA/mlx5: Support optional-counters binding for QPs
config: powerpc64-randconfig-001-20250307 (https://download.01.org/0day-ci/archive/20250307/202503071503.PnhQY3CE-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 14170b16028c087ca154878f5ed93d3089a965c6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250307/202503071503.PnhQY3CE-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503071503.PnhQY3CE-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "mlx5r_fs_bind_op_fc" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
>> ERROR: modpost: "mlx5r_fs_destroy_fcs" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
>> ERROR: modpost: "mlx5r_fs_unbind_op_fc" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
ERROR: modpost: "ib_create_ucap" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
ERROR: modpost: "ib_remove_ucap" [drivers/infiniband/hw/mlx5/mlx5_ib.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-07 7: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=202503071503.PnhQY3CE-lkp@intel.com \
--to=lkp@intel.com \
--cc=leon@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mbloch@nvidia.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=phaddad@nvidia.com \
/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