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/2][pull request] Intel Wired LAN Driver Updates 2022-06-07
Date: Thu, 09 Jun 2022 04:10:13 +0000 [thread overview]
Message-ID: <165474781381.435.16953073380913064415.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220607181538.748786-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 Tue, 7 Jun 2022 11:15:36 -0700 you wrote:
> This series contains updates to ixgbe driver only.
>
> Olivier Matz resolves an issue so that broadcast packets can still be
> received when VF removes promiscuous settings and removes setting of
> VLAN promiscuous, in promiscuous mode, to prevent a loop when VFs are
> bridged.
>
> [...]
Here is the summary with links:
- [net,1/2] ixgbe: fix bcast packets Rx on VF after promisc removal
https://git.kernel.org/netdev/net/c/803e9895ea2b
- [net,2/2] ixgbe: fix unexpected VLAN Rx in promisc mode on VF
https://git.kernel.org/netdev/net/c/7bb0fb7c63df
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 18:15 [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-06-07 Tony Nguyen
2022-06-07 18:15 ` [PATCH net 1/2] ixgbe: fix bcast packets Rx on VF after promisc removal Tony Nguyen
2022-06-07 18:15 ` [PATCH net 2/2] ixgbe: fix unexpected VLAN Rx in promisc mode on VF 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=165474781381.435.16953073380913064415.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.