public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	stable@vger.kernel.org,
	Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	intel-wired-lan@osuosl.org
Subject: Re: [PATCH net 0/2] ixgbe: fix promiscuous mode on VF
Date: Wed, 6 Apr 2022 10:18:14 +0200	[thread overview]
Message-ID: <Yk1MxlsbGi810tgb@arsenic.home> (raw)
In-Reply-To: <20220325140250.21663-1-olivier.matz@6wind.com>

Hi,

On Fri, Mar 25, 2022 at 03:02:48PM +0100, 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: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> 
> 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(-)

Sorry, the intel-wired-lan mailing list was not CC'ed initially.

Please let me know if I need to resend the patchset.

Thanks,
Olivier

  parent reply	other threads:[~2022-04-06 11:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 14:02 [PATCH net 0/2] ixgbe: fix promiscuous mode on VF Olivier Matz
2022-03-25 14:02 ` [PATCH net 1/2] ixgbe: fix bcast packets Rx on VF after promisc removal Olivier Matz
2022-03-25 14:02 ` [PATCH net 2/2] ixgbe: fix unexpected VLAN Rx in promisc mode on VF Olivier Matz
2022-04-06  8:18 ` Olivier Matz [this message]
2022-04-06  9:00   ` [Intel-wired-lan] [PATCH net 0/2] ixgbe: fix promiscuous " Paul Menzel

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=Yk1MxlsbGi810tgb@arsenic.home \
    --to=olivier.matz@6wind.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=h-shimamoto@ct.jp.nec.com \
    --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=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