All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
	Kashyap Desai <kashyap.desai@broadcom.com>,
	kernel test robot <lkp@intel.com>,
	linux-rdma@vger.kernel.org,
	Selvin Xavier <selvin.xavier@broadcom.com>
Subject: Re: [PATCH rdma-rc] RDMA/bnxt_re: Remove unusable nq variable
Date: Thu, 10 Apr 2025 20:30:40 -0300	[thread overview]
Message-ID: <20250410233040.GA88221@nvidia.com> (raw)
In-Reply-To: <8a4343e217d7d1c0a5a786b785c4ac57cb72a2a0.1744288299.git.leonro@nvidia.com>

On Thu, Apr 10, 2025 at 03:32:20PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Remove nq variable from bnxt_re_create_srq() and bnxt_re_destroy_srq()
> as it generates the following compilation warnings:
> 
> >> drivers/infiniband/hw/bnxt_re/ib_verbs.c:1777:24: warning: variable
> 'nq' set but not used [-Wunused-but-set-variable]
>     1777 |         struct bnxt_qplib_nq *nq = NULL;
>          |                               ^
>    drivers/infiniband/hw/bnxt_re/ib_verbs.c:1828:24: warning: variable
> 'nq' set but not used [-Wunused-but-set-variable]
>     1828 |         struct bnxt_qplib_nq *nq = NULL;
>          |                               ^
>    2 warnings generated.
> 
> Fixes: 6b395d31146a ("RDMA/bnxt_re: Fix budget handling of notification queue")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202504091055.CzgXnk4C-lkp@intel.com/
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
>  drivers/infiniband/hw/bnxt_re/ib_verbs.c | 5 -----
>  1 file changed, 5 deletions(-)

Applied to for-next, thanks

Jason

  reply	other threads:[~2025-04-10 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 12:32 [PATCH rdma-rc] RDMA/bnxt_re: Remove unusable nq variable Leon Romanovsky
2025-04-10 23:30 ` Jason Gunthorpe [this message]
2025-04-11  2:56 ` Kalesh Anakkur Purayil

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=20250410233040.GA88221@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=selvin.xavier@broadcom.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 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.