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, sassmann@redhat.com
Subject: Re: [PATCH net-next v2 0/2][pull request] 40GbE Intel Wired LAN Driver Updates 2022-06-07
Date: Thu, 09 Jun 2022 04:10:14 +0000 [thread overview]
Message-ID: <165474781446.435.4802491825076485771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220607175506.696671-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Tue, 7 Jun 2022 10:55:04 -0700 you wrote:
> This series contains updates to i40e and iavf drivers.
>
> Mateusz adds implementation for setting VF VLAN pruning to allow user to
> specify visibility of VLAN tagged traffic to VFs for i40e. He also adds
> waiting for result from PF for setting MAC address in iavf.
> ---
> v2: Rewrote some code to avoid passing a value as a condition (patch 2)
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] i40e: Add VF VLAN pruning
https://git.kernel.org/netdev/net-next/c/c87c938f62d8
- [net-next,v2,2/2] iavf: Add waiting for response from PF in set mac
https://git.kernel.org/netdev/net-next/c/35a2443d0910
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-06-09 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 17:55 [PATCH net-next v2 0/2][pull request] 40GbE Intel Wired LAN Driver Updates 2022-06-07 Tony Nguyen
2022-06-07 17:55 ` [PATCH net-next v2 1/2] i40e: Add VF VLAN pruning Tony Nguyen
2022-06-07 17:55 ` [PATCH net-next v2 2/2] iavf: Add waiting for response from PF in set mac Tony Nguyen
2022-06-09 4:10 ` 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=165474781446.435.4802491825076485771.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 \
--cc=sassmann@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.