From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: netdev@vger.kernel.org,
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
intel-wired-lan@osuosl.org, stable@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net 0/2] ixgbe: fix promiscuous mode on VF
Date: Wed, 6 Apr 2022 11:00:15 +0200 [thread overview]
Message-ID: <d8571528-4202-e6d7-e8b2-f9feb7e6f8f7@molgen.mpg.de> (raw)
In-Reply-To: <Yk1MxlsbGi810tgb@arsenic.home>
Dear Olivier,
Am 06.04.22 um 10:18 schrieb Olivier Matz:
> 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.
Yes, please resend.
Kind regards,
Paul
prev parent reply other threads:[~2022-04-06 12:48 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 ` [PATCH net 0/2] ixgbe: fix promiscuous " Olivier Matz
2022-04-06 9:00 ` Paul Menzel [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=d8571528-4202-e6d7-e8b2-f9feb7e6f8f7@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=davem@davemloft.net \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=intel-wired-lan@osuosl.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=olivier.matz@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