From: Jakub Kicinski <kuba@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,
pabeni@redhat.com, allen.hubbe@amd.com, nikhil.agarwal@amd.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [for-next v6 0/2] Add Reorder Completion Queue (RCQ) support
Date: Thu, 20 Aug 2026 13:08:17 -0700 [thread overview]
Message-ID: <20260820130817.43317368@kernel.org> (raw)
In-Reply-To: <c565fa0c-08e7-60b9-90e9-07daa4777a48@amd.com>
On Mon, 17 Aug 2026 12:35:52 +0530 Abhijit Gangurde wrote:
> On 8/14/26 22:54, Jakub Kicinski wrote:
> > On Thu, 13 Aug 2026 16:19:52 +0530 Abhijit Gangurde wrote:
> >> Patch 1 extends the net/ionic firmware identity structure to expose the
> >> rcq_sign_bit field from the RDMA LIF identity.
> > I asked for a PR, based on a tag from Linus's tree with that patch.
> > Did you send that?
> >
> > I only see a PR for rdma-core here
>
> Hi Jakub,
>
> I have the PR ready on Linus's v7.2 tag.
>
> The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
>
> Linux 7.2 (2026-08-16 14:32:26 -0700)
>
> are available in the Git repository at:
>
> https://github.com/abhijitG-xlnx/linux.git ionic_rcq_shared
>
> for you to fetch changes up to bb23acfd05f0399f33dae000df2ef4a88787b7d0:
>
> net: ionic: Fetch RCQ sign bit from firmware (2026-08-17 10:58:31 +0530)
Thanks! Pulled
next prev parent reply other threads:[~2026-08-20 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 10:49 [for-next v6 0/2] Add Reorder Completion Queue (RCQ) support Abhijit Gangurde
2026-08-13 10:49 ` [for-next v6 1/2] net: ionic: Fetch RCQ sign bit from firmware Abhijit Gangurde
2026-08-13 10:49 ` [for-next v6 2/2] RDMA/ionic: Add RCQ userspace support Abhijit Gangurde
2026-08-14 17:24 ` [for-next v6 0/2] Add Reorder Completion Queue (RCQ) support Jakub Kicinski
2026-08-17 7:05 ` Abhijit Gangurde
2026-08-20 20:08 ` Jakub Kicinski [this message]
2026-08-28 9:02 ` Abhijit Gangurde
2026-08-28 9:22 ` Leon Romanovsky
2026-09-01 10:14 ` 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=20260820130817.43317368@kernel.org \
--to=kuba@kernel.org \
--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 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.