From: Olivier Matz <olivier.matz@6wind.com>
To: netdev@vger.kernel.org
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
intel-wired-lan@osuosl.org, Paul Menzel <pmenzel@molgen.mpg.de>,
stable@vger.kernel.org,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH net v2 0/2] ixgbe: fix promiscuous mode on VF
Date: Mon, 25 Apr 2022 13:51:52 +0200 [thread overview]
Message-ID: <YmaLWN0aGIKCzkHP@platinum> (raw)
In-Reply-To: <20220406095252.22338-1-olivier.matz@6wind.com>
Hi,
On Wed, Apr 06, 2022 at 11:52:50AM +0200, Olivier Matz wrote:
> These 2 patches fix issues related to the promiscuous mode on VF.
>
> Comments are welcome,
> Olivier
>
> Cc: stable@vger.kernel.org
> Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
> Changes since v1:
> - resend with CC intel-wired-lan
> - remove CC Hiroshi Shimamoto (address does not exist anymore)
>
> Olivier Matz (2):
> ixgbe: fix bcast packets Rx on VF after promisc removal
> ixgbe: fix unexpected VLAN Rx in promisc mode on VF
>
> drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Any feedback about this patchset?
Comments are welcome.
Thanks,
Olivier
next prev parent reply other threads:[~2022-04-25 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 9:52 [PATCH net v2 0/2] ixgbe: fix promiscuous mode on VF Olivier Matz
2022-04-06 9:52 ` [PATCH net v2 1/2] ixgbe: fix bcast packets Rx on VF after promisc removal Olivier Matz
2022-06-06 11:43 ` [Intel-wired-lan] " Jankowski, Konrad0
2022-04-06 9:52 ` [PATCH net v2 2/2] ixgbe: fix unexpected VLAN Rx in promisc mode on VF Olivier Matz
2022-06-06 11:45 ` [Intel-wired-lan] " Jankowski, Konrad0
2022-04-25 11:51 ` Olivier Matz [this message]
2022-05-24 7:37 ` [PATCH net v2 0/2] ixgbe: fix promiscuous " Olivier Matz
2022-05-24 17:57 ` Jakub Kicinski
2022-05-26 14:10 ` [Intel-wired-lan] " Piotr Skajewski
2022-05-29 19:03 ` Olivier Matz
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=YmaLWN0aGIKCzkHP@platinum \
--to=olivier.matz@6wind.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@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).