From: kernel test robot <lkp@intel.com>
To: Leon Romanovsky <leonro@nvidia.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [leon-rdma:refactor-umem-v2 87/107] drivers/infiniband/hw/hns/hns_roce_hw_v2.c:2922:44: error: too many arguments to function call, expected 2, have 3
Date: Mon, 16 Feb 2026 03:47:06 +0800 [thread overview]
Message-ID: <202602160332.1O2QNg1W-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git refactor-umem-v2
head: 6270611a6aa0e2a782cf3849ccd6ee63b7f36d19
commit: 3b2c97078b14fbbdd2a1ae8a0bcffa17c81f976c [87/107] RDMA/core: Remove legacy CQ creation fallback path
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20260216/202602160332.1O2QNg1W-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260216/202602160332.1O2QNg1W-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/202602160332.1O2QNg1W-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:2922:44: error: too many arguments to function call, expected 2, have 3
2922 | if (hns_roce_create_cq(cq, &cq_init_attr, NULL)) {
| ~~~~~~~~~~~~~~~~~~ ^~~~
include/linux/stddef.h:8:14: note: expanded from macro 'NULL'
8 | #define NULL ((void *)0)
| ^~~~~~~~~~~
drivers/infiniband/hw/hns/hns_roce_device.h:1295:5: note: 'hns_roce_create_cq' declared here
1295 | int hns_roce_create_cq(struct ib_cq *ib_cq, const struct ib_cq_init_attr *attr);
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +2922 drivers/infiniband/hw/hns/hns_roce_hw_v2.c
487d65090a3dce1 Yixing Liu 2022-11-26 2903
487d65090a3dce1 Yixing Liu 2022-11-26 2904 static struct ib_cq *free_mr_init_cq(struct hns_roce_dev *hr_dev)
487d65090a3dce1 Yixing Liu 2022-11-26 2905 {
487d65090a3dce1 Yixing Liu 2022-11-26 2906 struct hns_roce_v2_priv *priv = hr_dev->priv;
487d65090a3dce1 Yixing Liu 2022-11-26 2907 struct hns_roce_v2_free_mr *free_mr = &priv->free_mr;
487d65090a3dce1 Yixing Liu 2022-11-26 2908 struct ib_device *ibdev = &hr_dev->ib_dev;
487d65090a3dce1 Yixing Liu 2022-11-26 2909 struct ib_cq_init_attr cq_init_attr = {};
487d65090a3dce1 Yixing Liu 2022-11-26 2910 struct hns_roce_cq *hr_cq;
487d65090a3dce1 Yixing Liu 2022-11-26 2911 struct ib_cq *cq;
487d65090a3dce1 Yixing Liu 2022-11-26 2912
487d65090a3dce1 Yixing Liu 2022-11-26 2913 cq_init_attr.cqe = HNS_ROCE_FREE_MR_USED_CQE_NUM;
487d65090a3dce1 Yixing Liu 2022-11-26 2914
487d65090a3dce1 Yixing Liu 2022-11-26 2915 hr_cq = kzalloc(sizeof(*hr_cq), GFP_KERNEL);
1f505a4a4250798 luoqing 2025-06-05 2916 if (!hr_cq)
487d65090a3dce1 Yixing Liu 2022-11-26 2917 return NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2918
487d65090a3dce1 Yixing Liu 2022-11-26 2919 cq = &hr_cq->ib_cq;
487d65090a3dce1 Yixing Liu 2022-11-26 2920 cq->device = ibdev;
487d65090a3dce1 Yixing Liu 2022-11-26 2921
487d65090a3dce1 Yixing Liu 2022-11-26 @2922 if (hns_roce_create_cq(cq, &cq_init_attr, NULL)) {
487d65090a3dce1 Yixing Liu 2022-11-26 2923 ibdev_err(ibdev, "failed to create cq for free mr.\n");
487d65090a3dce1 Yixing Liu 2022-11-26 2924 kfree(hr_cq);
487d65090a3dce1 Yixing Liu 2022-11-26 2925 return NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2926 }
487d65090a3dce1 Yixing Liu 2022-11-26 2927 free_mr->rsv_cq = to_hr_cq(cq);
487d65090a3dce1 Yixing Liu 2022-11-26 2928 free_mr->rsv_cq->ib_cq.device = &hr_dev->ib_dev;
487d65090a3dce1 Yixing Liu 2022-11-26 2929 free_mr->rsv_cq->ib_cq.uobject = NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2930 free_mr->rsv_cq->ib_cq.comp_handler = NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2931 free_mr->rsv_cq->ib_cq.event_handler = NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2932 free_mr->rsv_cq->ib_cq.cq_context = NULL;
487d65090a3dce1 Yixing Liu 2022-11-26 2933 atomic_set(&free_mr->rsv_cq->ib_cq.usecnt, 0);
487d65090a3dce1 Yixing Liu 2022-11-26 2934
487d65090a3dce1 Yixing Liu 2022-11-26 2935 return cq;
487d65090a3dce1 Yixing Liu 2022-11-26 2936 }
487d65090a3dce1 Yixing Liu 2022-11-26 2937
:::::: The code at line 2922 was first introduced by commit
:::::: 487d65090a3dce1ae54946aded55d0f8ac87cbab RDMA/hns: Fix the gid problem caused by free mr
:::::: TO: Yixing Liu <liuyixing1@huawei.com>
:::::: CC: Jason Gunthorpe <jgg@nvidia.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-15 19:48 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=202602160332.1O2QNg1W-lkp@intel.com \
--to=lkp@intel.com \
--cc=leonro@nvidia.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.