From: Jason Gunthorpe <jgg@nvidia.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com,
kalesh-anakkur.purayil@broadcom.com,
Zhu Yanjun <yanjun.zhu@linux.dev>
Subject: Re: [PATCH for-rc v3 0/2] RDMA/bnxt_re: Bug fixes for 6.12 kernel
Date: Mon, 21 Oct 2024 13:34:14 -0300 [thread overview]
Message-ID: <20241021163414.GC40622@nvidia.com> (raw)
In-Reply-To: <1728912975-19346-1-git-send-email-selvin.xavier@broadcom.com>
On Mon, Oct 14, 2024 at 06:36:13AM -0700, Selvin Xavier wrote:
> 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
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2024-10-21 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:36 [PATCH for-rc v3 0/2] RDMA/bnxt_re: Bug fixes for 6.12 kernel Selvin Xavier
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 ` Jason Gunthorpe [this message]
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=20241021163414.GC40622@nvidia.com \
--to=jgg@nvidia.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.com \
--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 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.