From: Saeed Mahameed <saeed@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 v3 0/2] gve: Handle alternate miss-completions
Date: Tue, 15 Nov 2022 21:38:04 -0800 [thread overview]
Message-ID: <Y3R3PAwDe+6fFbBw@x130.lan> (raw)
In-Reply-To: <20221114233514.1913116-1-jeroendb@google.com>
On 14 Nov 15:35, Jeroen de Borst 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.
>
nit: you missed to document the 1st "new AdminQ command" patch which has
some special logic to validate driver/os version compatibility with the
device and if it's related to this cover-letter title if at all.
>Changed in v3:
>- Rewording cover letter
>- Added 'Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>'
>Changes in v2:
>- Changed the subject to include 'gve:'
>
>
>Jeroen de Borst (2):
> gve: Adding a new AdminQ command to verify driver
> gve: Handle alternate miss completions
>
> drivers/net/ethernet/google/gve/gve.h | 1 +
> drivers/net/ethernet/google/gve/gve_adminq.c | 19 +++++++
> drivers/net/ethernet/google/gve/gve_adminq.h | 51 ++++++++++++++++++
> .../net/ethernet/google/gve/gve_desc_dqo.h | 5 ++
> drivers/net/ethernet/google/gve/gve_main.c | 52 +++++++++++++++++++
> drivers/net/ethernet/google/gve/gve_tx_dqo.c | 18 ++++---
> 6 files changed, 140 insertions(+), 6 deletions(-)
>
>--
>2.38.1.431.g37b22c650d-goog
>
prev parent reply other threads:[~2022-11-16 5:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 23:35 [PATCH net-next v3 0/2] gve: Handle alternate miss-completions Jeroen de Borst
2022-11-14 23:35 ` [PATCH net-next v3 1/2] gve: Adding a new AdminQ command to verify driver Jeroen de Borst
2022-11-16 5:34 ` Saeed Mahameed
2022-11-14 23:35 ` [PATCH net-next v3 2/2] gve: Handle alternate miss completions Jeroen de Borst
2022-11-16 5:17 ` Saeed Mahameed
2022-11-16 16:23 ` Jeroen de Borst
2022-11-16 23:36 ` Saeed Mahameed
2022-11-16 5:38 ` Saeed Mahameed [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=Y3R3PAwDe+6fFbBw@x130.lan \
--to=saeed@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).