From: Selvin Xavier <selvin.xavier@broadcom.com>
To: leon@kernel.org, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org, andrew.gospodarek@broadcom.com,
Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH for-rc 0/5] RDMA/bnxt_re: Bug fixes
Date: Mon, 22 Jan 2024 20:54:32 -0800 [thread overview]
Message-ID: <1705985677-15551-1-git-send-email-selvin.xavier@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Includes some of the minor bug fixes in bnxt_re. Please
review and apply.
Thanks,
Selvin Xavier
Kalesh AP (5):
RDMA/bnxt_re: Avoid creating fence MR for newer adapters
RDMA/bnxt_re: Remove a redundant check inside bnxt_re_vf_res_config
RDMA/bnxt_re: Fix unconditional fence for newer adapters
RDMA/bnxt_re: Return error for SRQ resize
RDMA/bnxt_re: Add a missing check in bnxt_qplib_query_srq
drivers/infiniband/hw/bnxt_re/ib_verbs.c | 43 +++++++++++++++++++++-----------
drivers/infiniband/hw/bnxt_re/main.c | 3 ---
drivers/infiniband/hw/bnxt_re/qplib_fp.c | 3 ++-
3 files changed, 30 insertions(+), 19 deletions(-)
--
2.5.5
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4224 bytes --]
next reply other threads:[~2024-01-23 5:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 4:54 Selvin Xavier [this message]
2024-01-23 4:54 ` [PATCH for-rc 1/5] RDMA/bnxt_re: Avoid creating fence MR for newer adapters Selvin Xavier
2024-01-23 4:54 ` [PATCH for-rc 2/5] RDMA/bnxt_re: Remove a redundant check inside bnxt_re_vf_res_config Selvin Xavier
2024-01-23 4:54 ` [PATCH for-rc 3/5] RDMA/bnxt_re: Fix unconditional fence for newer adapters Selvin Xavier
2024-01-23 4:54 ` [PATCH for-rc 4/5] RDMA/bnxt_re: Return error for SRQ resize Selvin Xavier
2024-01-23 4:54 ` [PATCH for-rc 5/5] RDMA/bnxt_re: Add a missing check in bnxt_qplib_query_srq Selvin Xavier
2024-01-25 10:04 ` [PATCH for-rc 0/5] RDMA/bnxt_re: Bug fixes Leon Romanovsky
-- strict thread matches above, loose matches on Subject: below --
2024-12-04 7:54 Kalesh AP
2024-12-05 9:08 ` Leon Romanovsky
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=1705985677-15551-1-git-send-email-selvin.xavier@broadcom.com \
--to=selvin.xavier@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--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