From: Jason Gunthorpe <jgg@ziepe.ca>
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 v11 4/6] RDMA/bnxt_re: Refactor bnxt_re_create_cq()
Date: Wed, 11 Feb 2026 08:48:24 -0400 [thread overview]
Message-ID: <20260211124824.GH750753@ziepe.ca> (raw)
In-Reply-To: <CAHHeUGUSL9_p9JzY6+-B+RXDa55KfWCWmP7iV1K7_NVcCuMqVQ@mail.gmail.com>
On Wed, Feb 11, 2026 at 04:55:28PM +0530, Sriharsha Basavapatna wrote:
> Agreed; is it ok to do this clean up as a separate patch (or series)
> later, since it is not related to this series? And since it also
> involves several callers of bnxt_qplib_alloc_init_hwq()?
Yes do it later
Jason
next prev parent reply other threads:[~2026-02-11 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 16:59 [PATCH rdma-next v11 0/6] RDMA/bnxt_re: Support uapi extensions Sriharsha Basavapatna
2026-02-10 16:59 ` [PATCH rdma-next v11 1/6] RDMA/bnxt_re: Move the UAPI methods to a dedicated file Sriharsha Basavapatna
2026-02-10 16:59 ` [PATCH rdma-next v11 2/6] RDMA/bnxt_re: Refactor bnxt_qplib_create_qp() function Sriharsha Basavapatna
2026-02-10 16:59 ` [PATCH rdma-next v11 3/6] RDMA/bnxt_re: Support doorbell extensions Sriharsha Basavapatna
2026-02-10 16:59 ` [PATCH rdma-next v11 4/6] RDMA/bnxt_re: Refactor bnxt_re_create_cq() Sriharsha Basavapatna
2026-02-10 19:07 ` Jason Gunthorpe
2026-02-11 11:25 ` Sriharsha Basavapatna
2026-02-11 12:48 ` Jason Gunthorpe [this message]
2026-02-10 16:59 ` [PATCH rdma-next v11 5/6] RDMA/bnxt_re: Support dmabuf for CQ rings Sriharsha Basavapatna
2026-02-10 16:59 ` [PATCH rdma-next v11 6/6] RDMA/bnxt_re: Support application specific CQs Sriharsha Basavapatna
2026-02-10 19:14 ` Jason Gunthorpe
2026-02-11 11:24 ` Sriharsha Basavapatna
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=20260211124824.GH750753@ziepe.ca \
--to=jgg@ziepe.ca \
--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