DPDK patches and discussions
 help / color / mirror / Atom feed
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>
Subject: Re: [dpdk-dev] [PATCH v2] doc: fix a parameter name in testpmd guide
Date: Wed, 9 Jan 2019 11:00:52 +0000	[thread overview]
Message-ID: <5a24b62e-68ed-61cd-a822-79f0c57d710e@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260D4A2DE@IRSMSX108.ger.corp.intel.com>

On 1/4/2019 9:57 AM, Iremonger, Bernard wrote:
>> -----Original Message-----
>> From: Rami Rosen [mailto:ramirose@gmail.com]
>> Sent: Friday, January 4, 2019 9:11 AM
>> To: dev@dpdk.org
>> Cc: stable@dpdk.org; Iremonger, Bernard <bernard.iremonger@intel.com>;
>> Rami Rosen <ramirose@gmail.com>
>> Subject: [PATCH v2] doc: fix a parameter name in testpmd guide
>>
>> There is no parameter called "eth-peer-configfile" in testpmd. It should be "eth-
>> peers-configfile". See the usage() method in app/test-pmd/parameters.c.
>>
>> v2: Fix line too long in the patch commit log.
>>
>> Fixes: a67857e97ba8 ("doc: clarify usage of testpmd MAC forward mode")
>> 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.

  reply	other threads:[~2019-01-09 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04  9:10 Rami Rosen
2019-01-04  9:57 ` Iremonger, Bernard
2019-01-09 11:00   ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-04  9:10 Rami Rosen

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=5a24b62e-68ed-61cd-a822-79f0c57d710e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --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).