From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/nfp: add support for chaning MAC address
Date: Fri, 13 Apr 2018 18:02:32 +0100 [thread overview]
Message-ID: <9aa1ad5f-95d0-605e-26e5-5a823767f455@intel.com> (raw)
In-Reply-To: <1523617233-12228-1-git-send-email-alejandro.lucero@netronome.com>
On 4/13/2018 12:00 PM, Alejandro Lucero wrote:
> This patch allows to use another MAC address than the one coming
> with the NIC by default.
>
> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> ---
> drivers/net/nfp/nfp_net.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/net/nfp/nfp_net.c b/drivers/net/nfp/nfp_net.c
> index bedd4b6..7db438c 100644
> --- a/drivers/net/nfp/nfp_net.c
> +++ b/drivers/net/nfp/nfp_net.c
> @@ -109,6 +109,8 @@ static int nfp_net_rss_reta_write(struct rte_eth_dev *dev,
> uint16_t reta_size);
> static int nfp_net_rss_hash_write(struct rte_eth_dev *dev,
> struct rte_eth_rss_conf *rss_conf);
> +static void nfp_set_mac_addr(struct rte_eth_dev *dev,
> + struct ether_addr *mac_addr);
Hi Alejandro,
mac_addr_set dev_ops is changed in this release [1], new prototype is [2], patch
is still in next-net, can you please rebase this patch on latest next-net?
[1]
703ee2278382 ("ethdev: return diagnostic when setting MAC address")
https://dpdk.org/dev/patchwork/patch/37951/
[2]
typedef int (*eth_mac_addr_set_t)(struct rte_eth_dev *dev,
struct ether_addr *mac_addr);
next prev parent reply other threads:[~2018-04-13 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 11:00 Alejandro Lucero
2018-04-13 17:02 ` Ferruh Yigit [this message]
2018-04-13 17:06 ` Alejandro Lucero
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=9aa1ad5f-95d0-605e-26e5-5a823767f455@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.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).