Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Selvin Xavier <selvin.xavier@broadcom.com>
To: leon@kernel.org, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com,
	kalesh-anakkur.purayil@broadcom.com,
	sriharsha.basavapatna@broadcom.com,
	Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH 00/11] RDMA/bnxt_re: Generic driver fixes
Date: Wed, 10 Jun 2026 03:08:44 -0700	[thread overview]
Message-ID: <20260610100855.64212-1-selvin.xavier@broadcom.com> (raw)

Includes fixes for few issues pointed by sashiko. Also, some
generic fixes found during internal code reviews.

Please review and Apply.

Thanks,
Selvin Xavier

Selvin Xavier (11):
  RDMA/bnxt_re : Initialize dpi variable to zero
  RDMA/bnxt_re: Add ownership check while getting the CQ toggle page
  RDMA/bnxt_re: Add ownership check while getting the SRQ toggle page
  RDMA/bnxt_re: Avoid displaying the kernel pointer
  RDMA/bnxt_re: Add a max slot check for SQ
  RDMA/bnxt_re: Avoid repeated requests to allocate WC pages
  RDMA/bnxt_re: Avoid any race while handling the hash list of CQ
  RDMA/bnxt_re: Avoid any race while handling the hash list of SRQ
  RDMA/bnxt_re: Fix the cleanup upon error during srq create
  RDMA/bnxt_re: Fix the cleanup upon error during CQ create
  RDMA/bnxt_re: Fail DBR related page allocation UAPIs if the feature is
    disabled

 drivers/infiniband/hw/bnxt_re/bnxt_re.h  |  2 ++
 drivers/infiniband/hw/bnxt_re/ib_verbs.c | 35 ++++++++++++++++++++++--
 drivers/infiniband/hw/bnxt_re/ib_verbs.h |  2 ++
 drivers/infiniband/hw/bnxt_re/main.c     |  4 +--
 drivers/infiniband/hw/bnxt_re/qplib_sp.h |  1 +
 drivers/infiniband/hw/bnxt_re/uapi.c     | 19 ++++++++++++-
 6 files changed, 57 insertions(+), 6 deletions(-)

-- 
2.39.3


             reply	other threads:[~2026-06-10  4:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 10:08 Selvin Xavier [this message]
2026-06-10 10:08 ` [PATCH 01/11] RDMA/bnxt_re : Initialize dpi variable to zero Selvin Xavier
2026-06-10 10:08 ` [PATCH 02/11] RDMA/bnxt_re: Add ownership check while getting the CQ toggle page Selvin Xavier
2026-06-10 10:08 ` [PATCH 03/11] RDMA/bnxt_re: Add ownership check while getting the SRQ " Selvin Xavier
2026-06-10 10:08 ` [PATCH 04/11] RDMA/bnxt_re: Avoid displaying the kernel pointer Selvin Xavier
2026-06-10 10:08 ` [PATCH 05/11] RDMA/bnxt_re: Add a max slot check for SQ Selvin Xavier
2026-06-10 10:08 ` [PATCH 06/11] RDMA/bnxt_re: Avoid repeated requests to allocate WC pages Selvin Xavier
2026-06-10  6:19   ` Selvin Xavier
2026-06-10 10:08 ` [PATCH 07/11] RDMA/bnxt_re: Avoid any race while handling the hash list of CQ Selvin Xavier
2026-06-10 10:08 ` [PATCH 08/11] RDMA/bnxt_re: Avoid any race while handling the hash list of SRQ Selvin Xavier
2026-06-10 10:08 ` [PATCH 09/11] RDMA/bnxt_re: Fix the cleanup upon error during srq create Selvin Xavier
2026-06-10 10:08 ` [PATCH 10/11] RDMA/bnxt_re: Fix the cleanup upon error during CQ create Selvin Xavier
2026-06-10 10:08 ` [PATCH 11/11] RDMA/bnxt_re: Fail DBR related page allocation UAPIs if the feature is disabled Selvin Xavier

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=20260610100855.64212-1-selvin.xavier@broadcom.com \
    --to=selvin.xavier@broadcom.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=jgg@ziepe.ca \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sriharsha.basavapatna@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox