From: sashiko-bot@kernel.org
To: "Abhijit Gangurde" <abhijit.gangurde@amd.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [for-next v4 3/5] RDMA/ionic: segregate rq related fields from ionic_qp into a new ionic_rq struct
Date: Thu, 01 Oct 2026 09:24:17 +0000 [thread overview]
Message-ID: <20261001092417.9387C1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930092111.3176738-4-abhijit.gangurde@amd.com>
> From: Amit Kumar <a.k@amd.com>
>
> In preparation for SRQ support, segregate rq related fields from ionic_qp
> into a new ionic_rq struct. This refactoring enables both non-SRQ and
> future SRQ code to leverage the common rq init/destroy infrastructure
> around ionic_qp_rq_init/_destroy with no functional changes.
>
> Signed-off-by: Amit Kumar <a.k@amd.com>
> Signed-off-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930092111.3176738-1-abhijit.gangurde@amd.com?part=3
next prev parent reply other threads:[~2026-10-01 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:21 [for-next v4 0/5] RDMA/ionic: add SRQ support and firmware assigned CQ and SRQ IDs Abhijit Gangurde
2026-09-30 9:21 ` [for-next v4 1/5] net: ionic: Fetch qid allocation and SRQ capability from firmware Abhijit Gangurde
2026-10-01 9:24 ` sashiko-bot
2026-09-30 9:21 ` [for-next v4 2/5] RDMA/ionic: support firmware-assigned CQ IDs Abhijit Gangurde
2026-10-01 9:24 ` sashiko-bot
2026-09-30 9:21 ` [for-next v4 3/5] RDMA/ionic: segregate rq related fields from ionic_qp into a new ionic_rq struct Abhijit Gangurde
2026-10-01 9:24 ` sashiko-bot [this message]
2026-09-30 9:21 ` [for-next v4 4/5] RDMA/ionic: add Shared receive queue (SRQ) support Abhijit Gangurde
2026-10-01 9:24 ` sashiko-bot
2026-09-30 9:21 ` [for-next v4 5/5] RDMA/ionic: implement SRQ event handling support Abhijit Gangurde
2026-10-01 9:24 ` sashiko-bot
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=20261001092417.9387C1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.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