DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shrikrishna Khare <skhare@shri-linux.eng.vmware.com>
To: David Harton <dharton@cisco.com>
Cc: <skhare@vmware.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vmxnet3: mac address set fixes
Date: Sun, 10 Sep 2017 10:40:00 -0700	[thread overview]
Message-ID: <alpine.DEB.2.10.1709101039290.5989@shri-linux.eng.vmware.com> (raw)
In-Reply-To: <20170825185457.38261-1-dharton@cisco.com>



On Fri, 25 Aug 2017, David Harton wrote:

> Updated vmxnet3_mac_addr_set() to store the newly set MAC address.
> Modified vmxnet3_write_mac() so the h/w is updated in an endian
> neutral manner.
> 
> Signed-off-by: David Harton <dharton@cisco.com>

Acked-by: Shrikrishna Khare <skhare@vmware.com>

> ---
>  drivers/net/vmxnet3/vmxnet3_ethdev.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/vmxnet3/vmxnet3_ethdev.c b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> index 06735dd..6525bb2 100644
> --- a/drivers/net/vmxnet3/vmxnet3_ethdev.c
> +++ b/drivers/net/vmxnet3/vmxnet3_ethdev.c
> @@ -537,10 +537,10 @@ static int eth_vmxnet3_pci_remove(struct rte_pci_device *pci_dev)
>  		     addr[0], addr[1], addr[2],
>  		     addr[3], addr[4], addr[5]);
>  
> -	val = *(const uint32_t *)addr;
> +	memcpy(&val, addr, 4);
>  	VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_MACL, val);
>  
> -	val = (addr[5] << 8) | addr[4];
> +	memcpy(&val, addr + 4, 2);
>  	VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_MACH, val);
>  }
>  
> @@ -1146,6 +1146,8 @@ static int eth_vmxnet3_pci_remove(struct rte_pci_device *pci_dev)
>  {
>  	struct vmxnet3_hw *hw = dev->data->dev_private;
>  
> +	ether_addr_copy(mac_addr, (struct ether_addr *)(hw->perm_addr));
> +	ether_addr_copy(mac_addr, &dev->data->mac_addrs[0]);
>  	vmxnet3_write_mac(hw, mac_addr->addr_bytes);
>  }
>  
> -- 
> 1.8.3.1
> 
> 

  reply	other threads:[~2017-09-10 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 18:54 David Harton
2017-09-10 17:40 ` Shrikrishna Khare [this message]
2017-09-11 13:29   ` Ferruh Yigit

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=alpine.DEB.2.10.1709101039290.5989@shri-linux.eng.vmware.com \
    --to=skhare@shri-linux.eng.vmware.com \
    --cc=dev@dpdk.org \
    --cc=dharton@cisco.com \
    --cc=skhare@vmware.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).