From: Simon Horman <horms@kernel.org>
To: Shailend Chand <shailend@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
Willem de Bruijn <willemb@google.com>,
Jeroen de Borst <jeroendb@google.com>
Subject: Re: [PATCH net-next 2/6] gve: Refactor napi add and remove functions
Date: Tue, 23 Jan 2024 16:26:56 +0000 [thread overview]
Message-ID: <20240123162656.GC254773@kernel.org> (raw)
In-Reply-To: <20240122182632.1102721-3-shailend@google.com>
On Mon, Jan 22, 2024 at 06:26:28PM +0000, Shailend Chand wrote:
> This change makes the napi poll functions non-static and moves the
> gve_(add|remove)_napi functions to gve_utils.c, to make possible future
> "start queue" hooks in the datapath files.
>
> Signed-off-by: Shailend Chand <shailend@google.com>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> Reviewed-by: Jeroen de Borst <jeroendb@google.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-01-23 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:26 [PATCH net-next 0/6] gve: Alloc before freeing when changing config Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 1/6] gve: Define config structs for queue allocation Shailend Chand
2024-01-23 16:26 ` Simon Horman
2024-01-22 18:26 ` [PATCH net-next 2/6] gve: Refactor napi add and remove functions Shailend Chand
2024-01-23 16:26 ` Simon Horman [this message]
2024-01-22 18:26 ` [PATCH net-next 3/6] gve: Switch to config-aware queue allocation Shailend Chand
2024-01-23 16:27 ` Simon Horman
2024-01-22 18:26 ` [PATCH net-next 4/6] gve: Refactor gve_open and gve_close Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 5/6] gve: Alloc before freeing when adjusting queues Shailend Chand
2024-01-22 18:26 ` [PATCH net-next 6/6] gve: Alloc before freeing when changing features Shailend Chand
2024-01-24 1:50 ` [PATCH net-next 0/6] gve: Alloc before freeing when changing config patchwork-bot+netdevbpf
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=20240123162656.GC254773@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=jeroendb@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shailend@google.com \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).