From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Steve Shin <jonshin@cisco.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, iryzhov@nfware.com
Subject: Re: [dpdk-dev] [PATCH v5] ethdev: fix MAC address replay
Date: Mon, 30 Jan 2017 10:21:44 +0100 [thread overview]
Message-ID: <47951643.7rmjiFTVd8@xps13> (raw)
In-Reply-To: <20170127175729.17803-1-jonshin@cisco.com>
2017-01-27 09:57, Steve Shin:
> This patch fixes a bug in replaying MAC address to the hardware
> in rte_eth_dev_config_restore() routine. Added default MAC replay as well.
>
> Fixes: 4bdefaade6d1 ("ethdev: VMDQ enhancements")
>
> ---
> v2: Added default MAC replay & Code optimization.
> v3: Covered a case (ex, SR-IOV) where multiple pools
> exist in the mac_pool_sel array.
> v4: removed a coding style warning.
> v5: Added default MAC replay with dev_ops->mac_addr_add.
The changelog should be after the SoB,
because everything after --- is removed when applying.
> Signed-off-by: Steve Shin <jonshin@cisco.com>
I've added
Reviewed-by: Igor Ryzhov <iryzhov@nfware.com>
Applied, thanks
prev parent reply other threads:[~2017-01-30 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 18:47 [dpdk-dev] [PATCH] lib/librte_ether: error handling on " Steve Shin
2017-01-19 19:35 ` Steve Shin (jonshin)
2017-01-19 22:39 ` Igor Ryzhov
2017-01-20 2:30 ` Steve Shin (jonshin)
2017-01-20 12:17 ` Igor Ryzhov
2017-01-20 19:12 ` Steve Shin (jonshin)
2017-01-20 22:23 ` [dpdk-dev] [PATCH v2] ethdev: fix " Steve Shin
2017-01-23 8:50 ` Igor Ryzhov
2017-01-23 23:19 ` Steve Shin (jonshin)
2017-01-23 23:50 ` [dpdk-dev] [PATCH v3] " Steve Shin
2017-01-24 2:21 ` [dpdk-dev] [PATCH v4] " Steve Shin
2017-01-24 10:09 ` Igor Ryzhov
2017-01-24 13:21 ` Ferruh Yigit
2017-01-24 14:00 ` Igor Ryzhov
2017-01-25 10:25 ` Thomas Monjalon
2017-01-27 17:57 ` [dpdk-dev] [PATCH v5] " Steve Shin
2017-01-30 9:21 ` Thomas Monjalon [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=47951643.7rmjiFTVd8@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=iryzhov@nfware.com \
--cc=jonshin@cisco.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).