From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Abhijit Gangurde <abhijit.gangurde@amd.com>,
jgg@ziepe.ca, brett.creeley@amd.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, 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 0/5] RDMA/ionic: add SRQ support and firmware assigned CQ and SRQ IDs
Date: Tue, 29 Sep 2026 16:21:26 -0700 [thread overview]
Message-ID: <20260929162126.5b3ec458@kernel.org> (raw)
In-Reply-To: <20260929185857.GL563127@unreal>
On Tue, 29 Sep 2026 21:58:57 +0300 Leon Romanovsky wrote:
> > are available in the Git repository at:
> >
> > https://github.com/abhijitG-xlnx/linux.git ionic-shared
>
> It doesn't apply, please rebase and resend.
Let's pull the shared branch, and then they can repost the patches
themselves to RDMA? The branch should pull for both of us. Pulling now..
next prev parent reply other threads:[~2026-09-29 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:27 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-29 23:30 ` patchwork-bot+netdevbpf
2026-09-25 8:27 ` [for-next v3 2/5] RDMA/ionic: support firmware-assigned CQ IDs Abhijit Gangurde
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-25 8:28 ` [for-next v3 4/5] RDMA/ionic: add Shared receive queue (SRQ) support Abhijit Gangurde
2026-09-25 8:28 ` [for-next v3 5/5] RDMA/ionic: implement SRQ event handling support Abhijit Gangurde
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 [this message]
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=20260929162126.5b3ec458@kernel.org \
--to=kuba@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®