Netdev List
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@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, nikhil.agarwal@amd.com,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [for-next v4 0/2] Add Reorder Completion Queue (RCQ) support
Date: Thu, 30 Jul 2026 13:46:34 +0300	[thread overview]
Message-ID: <20260730104634.GP12003@unreal> (raw)
In-Reply-To: <20260727182825.7b9bdffe@kernel.org>

On Mon, Jul 27, 2026 at 06:28:25PM -0700, Jakub Kicinski wrote:
> On Tue, 21 Jul 2026 17:40:32 +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.
> 
> Can you apply this on a linux/master tag and send a PR so that
> both networking and RDMA can pull?

I reviewed this series multiple times and still do not feel
confident enough to apply it given the feedback on v1.

For now, I am waiting for Jason to return from vacation.

Thanks

> -- 
> pw-bot: nap

      parent reply	other threads:[~2026-07-30 10:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 12:10 [for-next v4 0/2] Add Reorder Completion Queue (RCQ) support Abhijit Gangurde
2026-07-21 12:10 ` [for-next v4 1/2] net: ionic: Fetch RCQ sign bit from firmware Abhijit Gangurde
2026-07-21 12:10 ` [for-next v4 2/2] RDMA/ionic: Add RCQ userspace support Abhijit Gangurde
2026-07-28  1:28 ` [for-next v4 0/2] Add Reorder Completion Queue (RCQ) support Jakub Kicinski
2026-07-28 11:18   ` Abhijit Gangurde
2026-07-28 22:10     ` Jakub Kicinski
2026-07-30  8:47       ` Abhijit Gangurde
2026-07-30 10:46   ` Leon Romanovsky [this message]

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=20260730104634.GP12003@unreal \
    --to=leon@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=kuba@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