From: Leon Romanovsky <leon@kernel.org>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
tangchengchang@huawei.com
Subject: Re: [PATCH for-next] RDMA/hns: Add 'static' declaration
Date: Thu, 15 Jan 2026 12:42:18 +0200 [thread overview]
Message-ID: <20260115104218.GD14359@unreal> (raw)
In-Reply-To: <20260115024154.1825736-1-huangjunxian6@hisilicon.com>
On Thu, Jan 15, 2026 at 10:41:54AM +0800, Junxian Huang wrote:
> Fix the following warnings:
>
> >> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:964:6: warning: no previous prototype for function 'hns_roce_v2_drain_rq' [-Wmissing-prototypes]
> void hns_roce_v2_drain_rq(struct ib_qp *ibqp)
> ^
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:964:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
> void hns_roce_v2_drain_rq(struct ib_qp *ibqp)
> ^
> static
> >> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1001:6: warning: no previous prototype for function 'hns_roce_v2_drain_sq' [-Wmissing-prototypes]
> void hns_roce_v2_drain_sq(struct ib_qp *ibqp)
> ^
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c:1001:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
> void hns_roce_v2_drain_sq(struct ib_qp *ibqp)
> ^
> static
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202601150334.jRDP5xSy-lkp@intel.com/
> Fixes: cfa74ad31baa ("RDMA/hns: Support drain SQ and RQ")
> Signed-off-by: Junxian Huang <huangjunxian6@hisilicon.com>
> ---
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I squashed it and rebased my wip/leon-for-next branch.
Thanks
prev parent reply other threads:[~2026-01-15 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 2:41 [PATCH for-next] RDMA/hns: Add 'static' declaration Junxian Huang
2026-01-15 10:42 ` Leon Romanovsky [this message]
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=20260115104218.GD14359@unreal \
--to=leon@kernel.org \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=tangchengchang@huawei.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