From: patchwork-bot+netdevbpf@kernel.org
To: Jeroen de Borst <jeroendb@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jesse.brandeburg@intel.com
Subject: Re: [PATCH net-next v5 0/2] Handle alternate miss-completions
Date: Mon, 21 Nov 2022 11:00:16 +0000 [thread overview]
Message-ID: <166902841607.19060.3962341390969710942.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221117162701.2356849-1-jeroendb@google.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 17 Nov 2022 08:26:59 -0800 you wrote:
> Some versions of the virtual NIC present miss-completions in
> an alternative way. Let the diver handle these alternate completions
> and announce this capability to the device.
>
> The capability is announced uing a new AdminQ command that sends
> driver information to the device. The device can refuse a driver
> if it is lacking support for a capability, or it can adopt it's
> behavior to work around OS specific issues.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] gve: Adding a new AdminQ command to verify driver
https://git.kernel.org/netdev/net-next/c/c2a0c3ed5b64
- [net-next,v5,2/2] gve: Handle alternate miss completions
https://git.kernel.org/netdev/net-next/c/a5affbd8a73e
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:[~2022-11-21 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 16:26 [PATCH net-next v5 0/2] Handle alternate miss-completions Jeroen de Borst
2022-11-17 16:27 ` [PATCH net-next v5 1/2] gve: Adding a new AdminQ command to verify driver Jeroen de Borst
2022-11-20 19:40 ` Leon Romanovsky
2022-11-17 16:27 ` [PATCH net-next v5 2/2] gve: Handle alternate miss completions Jeroen de Borst
2022-11-21 11:00 ` 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=166902841607.19060.3962341390969710942.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jeroendb@google.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).