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,
Zhu Yanjun <yanjun.zhu@linux.dev>,
Selvin Xavier <selvin.xavier@broadcom.com>
Subject: [PATCH for-rc v3 0/2] RDMA/bnxt_re: Bug fixes for 6.12 kernel
Date: Mon, 14 Oct 2024 06:36:13 -0700 [thread overview]
Message-ID: <1728912975-19346-1-git-send-email-selvin.xavier@broadcom.com> (raw)
Hi,
Posting the v3 series for the 2 patches that was not merged from
the series. Please review and apply if it is okay to be merged.
Thanks,
Selvin Xavier
v2 - v3:
- Only the patches that got deferred from the previous posting of
this series
- Addressing Jason's comment to avoid using the lockdep
annotation for the new spin_lock, as this is not a nested
lock.
v1 - v2:
- Add a patch that removes irq variant of spinlock and use
spin_lock_bh as the control path processing happens from
tasklet context
- Address the comments from Zhu Yanjun by initializing the
newly added spin lock.
- One more fix included in the series
Selvin Xavier (2):
RDMA/bnxt_re: Fix the usage of control path spin locks
RDMA/bnxt_re: synchronize the qp-handle table array
drivers/infiniband/hw/bnxt_re/qplib_fp.c | 4 ++++
drivers/infiniband/hw/bnxt_re/qplib_rcfw.c | 38 +++++++++++++++---------------
drivers/infiniband/hw/bnxt_re/qplib_rcfw.h | 2 ++
3 files changed, 25 insertions(+), 19 deletions(-)
--
2.5.5
next reply other threads:[~2024-10-14 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:36 Selvin Xavier [this message]
2024-10-14 13:36 ` [PATCH for-rc v3 1/2] RDMA/bnxt_re: Fix the usage of control path spin locks Selvin Xavier
2024-10-14 13:36 ` [PATCH for-rc v3 2/2] RDMA/bnxt_re: synchronize the qp-handle table array Selvin Xavier
2024-10-21 16:34 ` [PATCH for-rc v3 0/2] RDMA/bnxt_re: Bug fixes for 6.12 kernel Jason Gunthorpe
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=1728912975-19346-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 \
--cc=yanjun.zhu@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).