From: Paolo Abeni <pabeni@redhat.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-07-14 (i40e)
Date: Tue, 18 Jul 2023 12:14:35 +0200 [thread overview]
Message-ID: <8261532fc0923d3cd9a8937e66c2e8c7e2e1d3b2.camel@redhat.com> (raw)
In-Reply-To: <20230714201253.1717957-1-anthony.l.nguyen@intel.com>
Hi,
On Fri, 2023-07-14 at 13:12 -0700, Tony Nguyen wrote:
> This series contains updates to i40e driver only.
>
> Ivan Vecera adds waiting for VF to complete initialization on VF related
> configuration callbacks.
>
> The following are changes since commit 68af900072c157c0cdce0256968edd15067e1e5a:
> gve: trivial spell fix Recive to Receive
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 40GbE
>
> Ivan Vecera (2):
> i40e: Add helper for VF inited state check with timeout
> i40e: Wait for pending VF reset in VF set callbacks
>
> .../ethernet/intel/i40e/i40e_virtchnl_pf.c | 65 +++++++++++--------
> 1 file changed, 38 insertions(+), 27 deletions(-)
>
The series LGTM, but is targeting net-next while it looks like -net
material to me (except for the missing Fixes tag ;). Am I missing
something? Could you please clarify?
Thanks!
Paolo
next prev parent reply other threads:[~2023-07-18 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 20:12 [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-07-14 (i40e) Tony Nguyen
2023-07-14 20:12 ` [PATCH net-next v2 1/2] i40e: Add helper for VF inited state check with timeout Tony Nguyen
2023-07-14 20:12 ` [PATCH net-next v2 2/2] i40e: Wait for pending VF reset in VF set callbacks Tony Nguyen
2023-07-18 10:14 ` Paolo Abeni [this message]
2023-07-18 17:04 ` [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-07-14 (i40e) Tony Nguyen
2023-07-21 14:10 ` Ivan Vecera
2023-07-19 11:40 ` 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=8261532fc0923d3cd9a8937e66c2e8c7e2e1d3b2.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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).