DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ophir Munk <ophirmu@mellanox.com>
Cc: dev@dpdk.org, Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1 2/3] common/mlx5: move netlink files under Linux directory
Date: Wed, 27 May 2020 09:40:53 -0700	[thread overview]
Message-ID: <20200527094053.31ed998a@hermes.lan> (raw)
In-Reply-To: <20200527161425.22944-2-ophirmu@mellanox.com>

On Wed, 27 May 2020 16:14:24 +0000
Ophir Munk <ophirmu@mellanox.com> wrote:

> +	DRV_LOG(DEBUG,
> +		"Interface %u cannot %s MAC address"
> +		" %02X:%02X:%02X:%02X:%02X:%02X %s",
> +		iface_idx,
> +		add ? "add" : "remove",
> +		mac->addr_bytes[0], mac->addr_bytes[1],
> +		mac->addr_bytes[2], mac->addr_bytes[3],
> +		mac->addr_bytes[4], mac->addr_bytes[5],

There is a rte_ether_format_addr() for this.

  reply	other threads:[~2020-05-27 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 16:14 [dpdk-dev] [PATCH v1 1/3] common/mlx5: move glue " Ophir Munk
2020-05-27 16:14 ` [dpdk-dev] [PATCH v1 2/3] common/mlx5: move netlink " Ophir Munk
2020-05-27 16:40   ` Stephen Hemminger [this message]
2020-06-03  7:05     ` Ophir Munk
2020-05-27 16:14 ` [dpdk-dev] [PATCH v1 3/3] common/mlx5: split common file " Ophir Munk
2020-06-01  5:50 ` [dpdk-dev] [PATCH v2 0/3] Linux specific files moved & split Ophir Munk
2020-06-01  5:50   ` [dpdk-dev] [PATCH v2 1/3] common/mlx5: move glue files under Linux directory Ophir Munk
2020-06-01  5:50   ` [dpdk-dev] [PATCH v2 2/3] common/mlx5: move netlink " Ophir Munk
2020-06-01  5:50   ` [dpdk-dev] [PATCH v2 3/3] common/mlx5: split common file " Ophir Munk
2020-06-01  7:03   ` [dpdk-dev] [PATCH v2 0/3] Linux specific files moved & split Matan Azrad
2020-06-03 10:19   ` Raslan Darawsheh

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=20200527094053.31ed998a@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=ophirmu@mellanox.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).