From: Joe Damato <jdamato@fastly•com>
To: Haiyang Zhang <haiyangz@microsoft•com>
Cc: "netdev@vger•kernel.org" <netdev@vger•kernel.org>,
Shradha Gupta <shradhagupta@microsoft•com>,
Erni Sri Satya Vennela <ernis@microsoft•com>,
KY Srinivasan <kys@microsoft•com>, Wei Liu <wei.liu@kernel•org>,
Dexuan Cui <decui@microsoft•com>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
"open list:Hyper-V/Azure CORE AND DRIVERS"
<linux-hyperv@vger•kernel.org>,
open list <linux-kernel@vger•kernel.org>
Subject: Re: [RFC net-next 1/1] hv_netvsc: Link queues to NAPIs
Date: Thu, 26 Sep 2024 08:53:08 -0700 [thread overview]
Message-ID: <ZvWDZBHdiKLE8S29@LQ3V64L9R2> (raw)
In-Reply-To: <MW4PR21MB18590C4C1EDFF656E4600D62CA692@MW4PR21MB1859.namprd21.prod.outlook.com>
On Wed, Sep 25, 2024 at 07:39:03PM +0000, Haiyang Zhang wrote:
>
[...]
> The code change looks fine to me.
> @Shradha Gupta or @Erni Sri Satya Vennela, Do you have time to test this?
Haiyang, would you like me to include an acked-by or reviewed-by
from you for this patch when I send it when net-next reopens?
I've added Shradha's Tested-by.
next prev parent reply other threads:[~2024-09-26 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 23:48 [RFC net-next 0/1] hyperv: Link queues to NAPIs Joe Damato
2024-09-24 23:48 ` [RFC net-next 1/1] hv_netvsc: " Joe Damato
2024-09-25 19:39 ` Haiyang Zhang
2024-09-26 4:06 ` Shradha Gupta
2024-09-26 10:34 ` Shradha Gupta
2024-09-26 14:29 ` Haiyang Zhang
2024-09-26 15:41 ` Joe Damato
2024-09-26 15:53 ` Joe Damato [this message]
2024-09-26 16:45 ` Haiyang Zhang
2024-09-26 15:10 ` Simon Horman
2024-09-26 15:42 ` Joe Damato
2024-09-26 15:50 ` Joe Damato
2024-09-26 15:56 ` Simon Horman
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=ZvWDZBHdiKLE8S29@LQ3V64L9R2 \
--to=jdamato@fastly$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=decui@microsoft$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=ernis@microsoft$(echo .)com \
--cc=haiyangz@microsoft$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kys@microsoft$(echo .)com \
--cc=linux-hyperv@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=shradhagupta@microsoft$(echo .)com \
--cc=wei.liu@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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