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
Subject: Re: [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2022-12-05 (i40e)
Date: Wed, 07 Dec 2022 04:50:16 +0000 [thread overview]
Message-ID: <167038861644.25696.8432380905804887657.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221205212523.3197565-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Mon, 5 Dec 2022 13:25:20 -0800 you wrote:
> This series contains updates to i40e driver only.
>
> Michal clears XPS init flag on reset to allow for updated values to be
> written.
>
> Sylwester adds sleep to VF reset to resolve issue of VFs not getting
> resources.
>
> [...]
Here is the summary with links:
- [net,1/3] i40e: Fix not setting default xps_cpus after reset
https://git.kernel.org/netdev/net/c/82e0572b2302
- [net,2/3] i40e: Fix for VF MAC address 0
https://git.kernel.org/netdev/net/c/085019704720
- [net,3/3] i40e: Disallow ip4 and ip6 l4_4_bytes
https://git.kernel.org/netdev/net/c/d64aaf3f7869
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:[~2022-12-07 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:25 [PATCH net 0/3][pull request] Intel Wired LAN Driver Updates 2022-12-05 (i40e) Tony Nguyen
2022-12-05 21:25 ` [PATCH net 1/3] i40e: Fix not setting default xps_cpus after reset Tony Nguyen
2022-12-05 21:25 ` [PATCH net 2/3] i40e: Fix for VF MAC address 0 Tony Nguyen
2022-12-05 21:25 ` [PATCH net 3/3] i40e: Disallow ip4 and ip6 l4_4_bytes Tony Nguyen
2022-12-07 4:50 ` 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=167038861644.25696.8432380905804887657.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=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.