From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org, leonro@nvidia.com
Subject: Re: [PATCH net v2 0/3][pull request] Intel Wired LAN Driver Updates 2023-05-16
Date: Wed, 17 May 2023 08:30:20 +0000 [thread overview]
Message-ID: <168431222046.29655.11286696607461346863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230516173610.2706835-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Tue, 16 May 2023 10:36:07 -0700 you wrote:
> This series contains updates to ice and iavf drivers.
>
> Ahmed adds setting of missed condition for statistics which caused
> incorrect reporting of values for ice. For iavf, he removes a call to set
> VLAN offloads during re-initialization which can cause incorrect values
> to be set.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] ice: Fix stats after PF reset
https://git.kernel.org/netdev/net/c/ab7470bc6d8f
- [net,v2,2/3] ice: Fix ice VF reset during iavf initialization
https://git.kernel.org/netdev/net/c/7255355a0636
- [net,v2,3/3] iavf: send VLAN offloading caps once after VFR
https://git.kernel.org/netdev/net/c/7dcbdf29282f
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:[~2023-05-17 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:36 [PATCH net v2 0/3][pull request] Intel Wired LAN Driver Updates 2023-05-16 Tony Nguyen
2023-05-16 17:36 ` [PATCH net v2 1/3] ice: Fix stats after PF reset Tony Nguyen
2023-05-16 17:36 ` [PATCH net v2 2/3] ice: Fix ice VF reset during iavf initialization Tony Nguyen
2023-05-16 17:36 ` [PATCH net v2 3/3] iavf: send VLAN offloading caps once after VFR Tony Nguyen
2023-05-17 8:30 ` 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=168431222046.29655.11286696607461346863.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.