From: Rami Rosen <ramirose@gmail.com>
To: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
Cc: dev <dev@dpdk.org>, Reshma Pattan <reshma.pattan@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix interactive commands in testpmd guide
Date: Tue, 16 Apr 2019 10:32:51 +0300 [thread overview]
Message-ID: <CAHLOa7T9VGiEJ1FX_WEg372oqsDnKNQMFV0Q=LjNvvgOZz37QA@mail.gmail.com> (raw)
Message-ID: <20190416073251.skwrhCzcBaPNe4Og5DUGD_CW8_4f_VL6z4ZOdt2ii0A@z> (raw)
In-Reply-To: <1555396398-17880-1-git-send-email-agalyax.babu.radhakrishnan@intel.com>
On Tue, Apr 16, 2019 at 9:35 AM Agalya Babu RadhaKrishnan <
agalyax.babu.radhakrishnan@intel.com> wrote:
> From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
>
> Added some missing documentation for interactive mode commands
>
> Fixes: 01b2092a5e ("testpmd: add dump commands for debug")
> Fixes: caf05a1b86 ("app/testpmd: new command to dump log types")
>
> Signed-off-by: Agalya Babu RadhaKrishnan <
> agalyax.babu.radhakrishnan@intel.com>
> ---
>
> Thanks for this work!
Reviewed-by: Rami Rosen <ramirose@gmail.com>
next prev parent reply other threads:[~2019-04-16 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:33 Agalya Babu RadhaKrishnan
2019-04-16 6:33 ` Agalya Babu RadhaKrishnan
2019-04-16 7:32 ` Rami Rosen [this message]
2019-04-16 7:32 ` Rami Rosen
2019-04-16 15:05 ` Ferruh Yigit
2019-04-16 15:05 ` Ferruh Yigit
2019-04-17 9:25 ` Iremonger, Bernard
2019-04-17 9:25 ` Iremonger, Bernard
2019-04-18 19:51 ` Ferruh Yigit
2019-04-18 19:51 ` Ferruh Yigit
2019-04-23 10:44 ` [dpdk-dev] [PATCH v2] " Agalya Babu RadhaKrishnan
2019-04-23 10:44 ` Agalya Babu RadhaKrishnan
2019-04-23 11:38 ` Ferruh Yigit
2019-04-23 11:38 ` 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='CAHLOa7T9VGiEJ1FX_WEg372oqsDnKNQMFV0Q=LjNvvgOZz37QA@mail.gmail.com' \
--to=ramirose@gmail.com \
--cc=agalyax.babu.radhakrishnan@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=reshma.pattan@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).