From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Sun, GuinanX" <guinanx.sun@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Sun, GuinanX" <guinanx.sun@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] net/iavf: fix adding multicast MAC address
Date: Tue, 20 Oct 2020 09:06:07 +0000 [thread overview]
Message-ID: <d4abf49d299a4a7ba5e17837a062673d@intel.com> (raw)
In-Reply-To: <20201015084305.48257-1-guinanx.sun@intel.com>
> -----Original Message-----
> From: Guinan Sun <guinanx.sun@intel.com>
> Sent: Thursday, October 15, 2020 4:43 PM
> To: dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Wu, Jingjing <jingjing.wu@intel.com>; Sun, GuinanX <guinanx.sun@intel.com>
> Subject: [PATCH v4] net/iavf: fix adding multicast MAC address
>
> When the multicast address list is added, it will flush previous addresses first,
> and then add new ones.
> If the number of multicast address in the list exceeds the upper limit, it will
> cause failure, then need to roll back previous addresses. This patch fixes the
> issue.
>
> Fixes: 05e4c3aff35f ("net/iavf: support multicast configuration")
>
> Signed-off-by: Guinan Sun <guinanx.sun@intel.com>
> Tested-by: Peng Yuan <yuan.peng@intel.com>
> Acked-by: Beilei Xing <beilei.xing@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2020-10-20 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 2:02 [dpdk-dev] [PATCH] " Guinan Sun
2020-10-15 5:13 ` Peng, Yuan
2020-10-15 5:37 ` Xing, Beilei
2020-10-15 5:57 ` Sun, GuinanX
2020-10-15 6:43 ` Xing, Beilei
2020-10-15 6:46 ` Sun, GuinanX
2020-10-15 6:55 ` [dpdk-dev] [PATCH v2] " Guinan Sun
2020-10-15 8:13 ` [dpdk-dev] [PATCH v3] " Guinan Sun
2020-10-15 8:38 ` Xing, Beilei
2020-10-15 8:43 ` [dpdk-dev] [PATCH v4] " Guinan Sun
2020-10-20 9:06 ` Zhang, Qi Z [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=d4abf49d299a4a7ba5e17837a062673d@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=guinanx.sun@intel.com \
--cc=jingjing.wu@intel.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 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).