All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
	Pascal Mazon <pascal.mazon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] net/tap: add support for fixed mac addresses
Date: Tue, 11 Apr 2017 16:49:09 +0100	[thread overview]
Message-ID: <8fd87b23-4738-7b7c-de40-bb54539760dd@intel.com> (raw)
In-Reply-To: <AA7E2728-D9AA-466F-9E43-33FCF1D34063@intel.com>

On 4/11/2017 4:42 PM, Wiles, Keith wrote:
> 
>> On Apr 11, 2017, at 10:09 AM, Pascal Mazon <pascal.mazon@6wind.com> wrote:
>>
>> Support for a fixed MAC address for testing with the last octet
>> incrementing by one for each interface defined with the new 'mac=fixed'
>> string on the --vdev option. The default option is still to randomize
>> the MAC address for each tap interface.
>>
>> Signed-off-by: Keith Wiles <keith.wiles@intel.com>

<...>
> This does not show up as a change in the patch, I thought it should.

It does: http://dpdk.org/dev/patchwork/patch/23508/

  reply	other threads:[~2017-04-11 15:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 18:18 [PATCH] net/tap: add support for fixed mac addresses Keith Wiles
2017-04-11  7:18 ` Pascal Mazon
2017-04-11  8:31   ` Ferruh Yigit
2017-04-11 13:23   ` Wiles, Keith
2017-04-11 13:25     ` Wiles, Keith
2017-04-11 13:39     ` Ferruh Yigit
2017-04-11 13:41       ` Wiles, Keith
2017-04-11 13:54     ` Pascal Mazon
2017-04-11 14:17       ` Wiles, Keith
2017-04-11 15:09         ` Pascal Mazon
2017-04-11 15:38           ` Wiles, Keith
2017-04-11 15:42           ` Wiles, Keith
2017-04-11 15:49             ` Ferruh Yigit [this message]
2017-04-11 16:16           ` Wiles, Keith
2017-04-12  7:30           ` [PATCH v2] " Pascal Mazon
2017-04-14  9:45             ` Ferruh Yigit
2017-05-12 12:24             ` 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=8fd87b23-4738-7b7c-de40-bb54539760dd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=pascal.mazon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.