From: patchwork-bot+netdevbpf@kernel.org
To: Abhijit Gangurde <abhijit.gangurde@amd.com>
Cc: jgg@ziepe.ca, leon@kernel.org, brett.creeley@amd.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, allen.hubbe@amd.com,
a.k@amd.com, nikhil.agarwal@amd.com, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [for-next v3 1/5] net: ionic: Fetch qid allocation and SRQ capability from firmware
Date: Tue, 29 Sep 2026 23:30:05 +0000 [thread overview]
Message-ID: <179072460594.1164319.7269061494393053569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925082802.2675902-2-abhijit.gangurde@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Abhijit Gangurde <abhijit.gangurde@amd.com>:
On Fri, 25 Sep 2026 13:57:58 +0530 you wrote:
> Read the qid allocation and SRQ capability from the RDMA LIF identity
> reported by firmware.
>
> Signed-off-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
> ---
> .../net/ethernet/pensando/ionic/ionic_if.h | 31 +++++++++++++++++--
> 1 file changed, 29 insertions(+), 2 deletions(-)
Here is the summary with links:
- [for-next,v3,1/5] net: ionic: Fetch qid allocation and SRQ capability from firmware
https://git.kernel.org/netdev/net-next/c/c73a5f20bc78
- [for-next,v3,2/5] RDMA/ionic: support firmware-assigned CQ IDs
(no matching commit)
- [for-next,v3,3/5] RDMA/ionic: segregate rq related fields from ionic_qp into a new ionic_rq struct
(no matching commit)
- [for-next,v3,4/5] RDMA/ionic: add Shared receive queue (SRQ) support
(no matching commit)
- [for-next,v3,5/5] RDMA/ionic: implement SRQ event handling support
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-29 23:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:27 [for-next v3 0/5] RDMA/ionic: add SRQ support and firmware assigned CQ and SRQ IDs Abhijit Gangurde
2026-09-25 8:27 ` [for-next v3 1/5] net: ionic: Fetch qid allocation and SRQ capability from firmware Abhijit Gangurde
2026-09-26 8:29 ` sashiko-bot
2026-09-29 23:30 ` patchwork-bot+netdevbpf [this message]
2026-09-25 8:27 ` [for-next v3 2/5] RDMA/ionic: support firmware-assigned CQ IDs Abhijit Gangurde
2026-09-26 8:29 ` sashiko-bot
2026-09-25 8:28 ` [for-next v3 3/5] RDMA/ionic: segregate rq related fields from ionic_qp into a new ionic_rq struct Abhijit Gangurde
2026-09-26 8:29 ` sashiko-bot
2026-09-25 8:28 ` [for-next v3 4/5] RDMA/ionic: add Shared receive queue (SRQ) support Abhijit Gangurde
2026-09-26 8:29 ` sashiko-bot
2026-09-25 8:28 ` [for-next v3 5/5] RDMA/ionic: implement SRQ event handling support Abhijit Gangurde
2026-09-26 8:29 ` sashiko-bot
2026-09-29 18:58 ` [for-next v3 0/5] RDMA/ionic: add SRQ support and firmware assigned CQ and SRQ IDs Leon Romanovsky
2026-09-29 23:21 ` Jakub Kicinski
2026-09-30 13:11 ` Leon Romanovsky
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=179072460594.1164319.7269061494393053569.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.k@amd.com \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=pabeni@redhat.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 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.