From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Dekel Peled <dekelp@mellanox.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"orika@mellanox.com" <orika@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix typos in testpmd user guide
Date: Tue, 2 Apr 2019 16:32:50 +0100 [thread overview]
Message-ID: <ec8e9ae3-b92d-d782-458d-b5f71dff90f6@intel.com> (raw)
Message-ID: <20190402153250.NJPXwUGliObvE3dv_3O46y1iV2s2wimIEFegSJpLe7M@z> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D799E3@IRSMSX108.ger.corp.intel.com>
On 4/1/2019 5:19 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Dekel Peled
>> Sent: Sunday, March 31, 2019 11:21 AM
>> To: Wu, Jingjing <jingjing.wu@intel.com>; Lu, Wenzhuo
>> <wenzhuo.lu@intel.com>
>> Cc: dev@dpdk.org; orika@mellanox.com; stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH] doc: fix typos in testpmd user guide
>>
>> Correct typing mistakes in several places.
>> 1) "Those command will" ==> "These commands will"
>> 2) icmp6_nd_opt_sla_eth ==> icmp6_nd_opt_tla_eth
>> (change 's' to 't' for 'target' where applicable)
>>
>> Fixes: 1960be7d32f8 ("app/testpmd: add VXLAN encap/decap")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-02 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:20 [dpdk-dev] " Dekel Peled
2019-03-31 10:20 ` Dekel Peled
2019-04-01 16:19 ` Iremonger, Bernard
2019-04-01 16:19 ` Iremonger, Bernard
2019-04-02 15:32 ` Ferruh Yigit [this message]
2019-04-02 15:32 ` [dpdk-dev] [dpdk-stable] " 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=ec8e9ae3-b92d-d782-458d-b5f71dff90f6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--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).