From: Jakub Kicinski <kuba@kernel.org>
To: Long Li <longli@microsoft.com>
Cc: Konstantin Taranov <kotaranov@microsoft.com>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
KY Srinivasan <kys@microsoft.com>, Wei Liu <wei.liu@kernel.org>,
Dexuan Cui <DECUI@microsoft.com>,
"shradhagupta@linux.microsoft.com"
<shradhagupta@linux.microsoft.com>,
Simon Horman <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH net-next v11 0/6] net: mana: Per-vPort EQ and MSI-X management
Date: Tue, 2 Jun 2026 17:36:07 -0700 [thread overview]
Message-ID: <20260602173607.34063034@kernel.org> (raw)
In-Reply-To: <SA1PR21MB6683230E973519C12E2AB797CE122@SA1PR21MB6683.namprd21.prod.outlook.com>
On Tue, 2 Jun 2026 22:48:05 +0000 Long Li wrote:
> Changes in patch 6 from v2 to v11:
>
> - Error handling updated from NULL/-ENOMEM to IS_ERR()/PTR_ERR() for mana_gd_get_gic() return values
> - Added mdev->eqs[i]->eq.irq = gic->irq to populate the irq field on all RDMA EQs for consistency with the Ethernet path
> - Introduced a separate msi variable instead of modifying spec.eq.msix_index directly
> - Commit message updated
>
> The gdma.h changes are identical to v2.
Hm, yes, Leon seems to be AFK since May 19th.
Please repost with his tag included, the list of changes you provided
does seem immaterial. I don't want to merge v11 as is, there's a good
chance people marked this thread as ignored by now.
prev parent reply other threads:[~2026-06-03 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 2:02 [PATCH net-next v11 0/6] net: mana: Per-vPort EQ and MSI-X management Long Li
2026-05-23 2:02 ` [PATCH net-next v11 1/6] net: mana: Create separate EQs for each vPort Long Li
2026-05-30 0:46 ` sashiko-bot
2026-05-23 2:02 ` [PATCH net-next v11 2/6] net: mana: Query device capabilities and configure MSI-X sharing for EQs Long Li
2026-05-23 2:02 ` [PATCH net-next v11 3/6] net: mana: Introduce GIC context with refcounting for interrupt management Long Li
2026-05-23 2:02 ` [PATCH net-next v11 4/6] net: mana: Use GIC functions to allocate global EQs Long Li
2026-05-23 2:02 ` [PATCH net-next v11 5/6] net: mana: Allocate interrupt context for each EQ when creating vPort Long Li
2026-05-23 2:02 ` [PATCH net-next v11 6/6] RDMA/mana_ib: Allocate interrupt contexts on EQs Long Li
2026-05-28 2:27 ` [PATCH net-next v11 0/6] net: mana: Per-vPort EQ and MSI-X management Jakub Kicinski
2026-05-28 22:05 ` [EXTERNAL] " Long Li
2026-06-02 22:48 ` Long Li
2026-06-03 0:36 ` Jakub Kicinski [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=20260602173607.34063034@kernel.org \
--to=kuba@kernel.org \
--cc=DECUI@microsoft.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kotaranov@microsoft.com \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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