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,
	Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH rdma-rc 0/3] RDMA/bnxt_re: Bug fixes
Date: Mon,  3 Mar 2025 08:59:35 -0800	[thread overview]
Message-ID: <1741021178-2569-1-git-send-email-selvin.xavier@broadcom.com> (raw)

Includes some of the critical fixes found while testing
with increased resource limits. Please review and apply.

Thanks,
Selvin Xavier

Kashyap Desai (2):
  RDMA/bnxt_re: Fix allocation of QP table
  RDMA/bnxt_re: Add missing paranthesis in map_qp_id_to_tbl_indx

Preethi G (1):
  RDMA/bnxt_re: Fix reporting maximum SRQs on P7 chips

 drivers/infiniband/hw/bnxt_re/bnxt_re.h    |  6 ------
 drivers/infiniband/hw/bnxt_re/main.c       |  3 +--
 drivers/infiniband/hw/bnxt_re/qplib_rcfw.c | 10 +---------
 drivers/infiniband/hw/bnxt_re/qplib_rcfw.h |  6 +++---
 drivers/infiniband/hw/bnxt_re/qplib_res.c  |  9 +++++++++
 drivers/infiniband/hw/bnxt_re/qplib_res.h  | 12 ++++++++++++
 drivers/infiniband/hw/bnxt_re/qplib_sp.c   |  3 +++
 drivers/infiniband/hw/bnxt_re/roce_hsi.h   |  3 ++-
 8 files changed, 31 insertions(+), 21 deletions(-)

-- 
2.5.5


             reply	other threads:[~2025-03-03 17:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 16:59 Selvin Xavier [this message]
2025-03-03 16:59 ` [PATCH rdma-rc 1/3] RDMA/bnxt_re: Fix allocation of QP table Selvin Xavier
2025-03-03 16:59 ` [PATCH rdma-rc 2/3] RDMA/bnxt_re: Add missing paranthesis in map_qp_id_to_tbl_indx Selvin Xavier
2025-03-03 16:59 ` [PATCH rdma-rc 3/3] RDMA/bnxt_re: Fix reporting maximum SRQs on P7 chips Selvin Xavier
2025-03-03 19:18 ` [PATCH rdma-rc 0/3] RDMA/bnxt_re: Bug fixes Leon Romanovsky
  -- strict thread matches above, loose matches on Subject: below --
2021-08-18 20:57 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=1741021178-2569-1-git-send-email-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 \
    /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