From: Leon Romanovsky <leon@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 v4 0/2] Handle alternate miss-completions
Date: Thu, 17 Nov 2022 13:10:21 +0200 [thread overview]
Message-ID: <Y3YWnS1ZEY8ocXCQ@unreal> (raw)
In-Reply-To: <20221116181725.2207544-1-jeroendb@google.com>
On Wed, Nov 16, 2022 at 10:17:23AM -0800, 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.
>
> 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 it.
>
> Changed in v4:
> - Clarified new AdminQ command in cover letter
> - Changed EOPNOTSUPP to ENOTSUPP to match device's response
If you rely on the error code, please use the correct one and
fix the driver to use EOPNOTSUPP and not ENOTSUPP.
Thanks
prev parent reply other threads:[~2022-11-17 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 18:17 [PATCH net-next v4 0/2] Handle alternate miss-completions Jeroen de Borst
2022-11-16 18:17 ` [PATCH net-next v4 1/2] gve: Adding a new AdminQ command to verify driver Jeroen de Borst
2022-11-16 18:17 ` [PATCH net-next v4 2/2] gve: Handle alternate miss completions Jeroen de Borst
2022-11-17 11:12 ` Leon Romanovsky
2022-11-17 11:10 ` Leon Romanovsky [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=Y3YWnS1ZEY8ocXCQ@unreal \
--to=leon@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).