From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <jdamato@fastly.com>
Cc: netdev@vger.kernel.org, mkarsten@uwaterloo.ca,
gerhard@engleder-embedded.com, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com, kuba@kernel.org, mst@redhat.com,
leiyang@redhat.com, ast@kernel.org, andrew+netdev@lunn.ch,
bpf@vger.kernel.org, daniel@iogearbox.net, davem@davemloft.net,
edumazet@google.com, eperezma@redhat.com, hawk@kernel.org,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
pabeni@redhat.com, virtualization@lists.linux.dev
Subject: Re: [PATCH net-next v6 0/4] virtio-net: Link queues to NAPIs
Date: Mon, 10 Mar 2025 20:20:41 +0000 [thread overview]
Message-ID: <174163804173.3681464.7169835373797288242.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250307011215.266806-1-jdamato@fastly.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Mar 2025 01:12:08 +0000 you wrote:
> Greetings:
>
> Welcome to v6. Only patch updated is patch 3. See changelog below.
>
> Jakub recently commented [1] that I should not hold this series on
> virtio-net linking queues to NAPIs behind other important work that is
> on-going and suggested I re-spin, so here we are :)
>
> [...]
Here is the summary with links:
- [net-next,v6,1/4] virtio-net: Refactor napi_enable paths
https://git.kernel.org/netdev/net-next/c/2af5adf962d4
- [net-next,v6,2/4] virtio-net: Refactor napi_disable paths
https://git.kernel.org/netdev/net-next/c/986a93045183
- [net-next,v6,3/4] virtio-net: Map NAPIs to queues
https://git.kernel.org/netdev/net-next/c/e7231f49d526
- [net-next,v6,4/4] virtio_net: Use persistent NAPI config
https://git.kernel.org/netdev/net-next/c/d5d715207e29
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-10 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 1:12 [PATCH net-next v6 0/4] virtio-net: Link queues to NAPIs Joe Damato
2025-03-07 6:48 ` Xuan Zhuo
2025-03-10 20:20 ` patchwork-bot+netdevbpf [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=174163804173.3681464.7169835373797288242.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=gerhard@engleder-embedded.com \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=jdamato@fastly.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=leiyang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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