From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] doc/guides: updated testpmd app user guide for vxlan/nvgre encap/decap
Date: Thu, 14 Jun 2018 18:14:18 +0100 [thread overview]
Message-ID: <68ba8380-fad4-addd-64bd-259e6f1fd183@intel.com> (raw)
In-Reply-To: <4706a44f-0ade-3d5c-6083-09da6dea119e@intel.com>
On 5/14/2018 4:42 PM, Mohammad Abdul Awal wrote:
>
>
> On 14/05/2018 11:35, Iremonger, Bernard wrote:
>> Hi Awal,
>>
>>> -----Original Message-----
>>> From: Awal, Mohammad Abdul
>>> Sent: Friday, May 11, 2018 6:14 PM
>>> To: dev@dpdk.org; Iremonger, Bernard <bernard.iremonger@intel.com>;
>>> adrien.mazarguil@6wind.com
>>> Subject: [PATCH v2 2/2] doc/guides: updated testpmd app user guide for
>>> vxlan/nvgre encap/decap
>>>
>>> Updated the testpmd user guide documentation with how to used new action
>> Typo, "used" in line above should be "use".
> Will fix.
Hi Awal,
If this is the only change I can fix this while merging. Are you planning a new
version of the set?
next prev parent reply other threads:[~2018-06-14 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 17:13 [dpdk-dev] [PATCH v2 0/2] Added vxlan/nvgre encap/decap support to testpmd Mohammad Abdul Awal
2018-05-11 17:14 ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: enabled vxlan and nvgre encap/decap support for rte_flow Mohammad Abdul Awal
2018-05-14 11:14 ` Iremonger, Bernard
2018-05-11 17:14 ` [dpdk-dev] [PATCH v2 2/2] doc/guides: updated testpmd app user guide for vxlan/nvgre encap/decap Mohammad Abdul Awal
2018-05-14 10:35 ` Iremonger, Bernard
2018-05-14 15:42 ` Mohammad Abdul Awal
2018-06-14 17:14 ` Ferruh Yigit [this message]
2018-06-14 17:19 ` Ferruh Yigit
2018-06-18 11:20 ` Mohammad Abdul Awal
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=68ba8380-fad4-addd-64bd-259e6f1fd183@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=mohammad.abdul.awal@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).