From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dekel Peled <dekelp@mellanox.com>,
wenzhuo.lu@intel.com, jingjing.wu@intel.com,
bernard.iremonger@intel.com, adrien.mazarguil@6wind.com
Cc: shahafs@mellanox.com, dev@dpdk.org, orika@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] doc: update testpmd user guide for clarity
Date: Mon, 5 Nov 2018 12:09:22 +0000 [thread overview]
Message-ID: <f71861d8-60f7-5204-38b3-fabe037fb58d@intel.com> (raw)
In-Reply-To: <1541326545-19533-1-git-send-email-dekelp@mellanox.com>
On 11/4/2018 10:15 AM, Dekel Peled wrote:
> The description of prefix for mask creation was misunderstood.
> I updated the description, so it is clearly understood which
> mask will be created by a certain prefix.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-11-05 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 10:15 Dekel Peled
2018-11-05 12:09 ` Ferruh Yigit [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=f71861d8-60f7-5204-38b3-fabe037fb58d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=wenzhuo.lu@intel.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).