From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Rami Rosen <ramirose@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH V2] doc: add missing loopback option in testpmd guide
Date: Thu, 17 Jan 2019 16:55:59 +0000 [thread overview]
Message-ID: <d856dc08-55d3-370e-8d50-04a0d1fb1acd@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D50A11@IRSMSX108.ger.corp.intel.com>
On 1/17/2019 1:24 PM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Rami Rosen [mailto:ramirose@gmail.com]
>> Sent: Thursday, January 17, 2019 11:39 AM
>> To: dev@dpdk.org
>> Cc: stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>;
>> Iremonger, Bernard <bernard.iremonger@intel.com>; Rami Rosen
>> <ramirose@gmail.com>
>> Subject: [PATCH V2] doc: add missing loopback option in testpmd guide
>>
>> This patch adds a missing topology "loop" mode for port-topology option in
>> testpmd guide. The testpmd "loop" option
>> (PORT_TOPOLOGY_LOOP) was added to testpmd parameter port-topology back
>> in 2014, but it seems that it was never added to the testpmd guide. This patch
>> adds it in the testpmd guide.
>>
>> v2: Change "loopback" to "loop" (following Bernard review)
>>
>> Fixes: 3e2006d6186c ("app/testpmd: add loopback topology")
>> Cc: stable@dpdk.org
>> Signed-off-by: Rami Rosen <ramirose@gmail.com>
>
> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-01-17 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 11:39 [dpdk-dev] " Rami Rosen
2019-01-17 13:24 ` Iremonger, Bernard
2019-01-17 16:55 ` 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=d856dc08-55d3-370e-8d50-04a0d1fb1acd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ramirose@gmail.com \
--cc=stable@dpdk.org \
/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).