From: Jason Gunthorpe <jgg@nvidia.com>
To: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, selvin.xavier@broadcom.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH rdma-next v14 0/6] RDMA/bnxt_re: Support uapi extensions
Date: Thu, 5 Mar 2026 20:47:33 -0400 [thread overview]
Message-ID: <20260306004733.GA2137346@nvidia.com> (raw)
In-Reply-To: <20260302110036.36387-1-sriharsha.basavapatna@broadcom.com>
On Mon, Mar 02, 2026 at 04:30:30PM +0530, Sriharsha Basavapatna wrote:
> Kalesh AP (3):
> RDMA/bnxt_re: Move the UAPI methods to a dedicated file
> RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function
> RDMA/bnxt_re: Support doorbell extensions
>
> Sriharsha Basavapatna (3):
> RDMA/bnxt_re: Refactor bnxt_re_create_cq()
> RDMA/bnxt_re: Separate kernel and user CQ creation paths
> RDMA/bnxt_re: Support application specific CQs
Applied to for next, but this last patch should have been split into
adding umem support and adding BNXT_RE_CQ_FIXED_NUM_CQE_ENABLE. One
idea per patch
Jason
prev parent reply other threads:[~2026-03-06 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 11:00 [PATCH rdma-next v14 0/6] RDMA/bnxt_re: Support uapi extensions Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 1/6] RDMA/bnxt_re: Move the UAPI methods to a dedicated file Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 2/6] RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 3/6] RDMA/bnxt_re: Support doorbell extensions Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 4/6] RDMA/bnxt_re: Refactor bnxt_re_create_cq() Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 5/6] RDMA/bnxt_re: Separate kernel and user CQ creation paths Sriharsha Basavapatna
2026-03-02 11:00 ` [PATCH rdma-next v14 6/6] RDMA/bnxt_re: Support application specific CQs Sriharsha Basavapatna
2026-03-06 0:47 ` 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=20260306004733.GA2137346@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=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