From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: "Xu, Rosen" <rosen.xu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Xu, Rosen" <rosen.xu@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] [PATCH v2 2/2] doc/guides/testpmd_app_ug: update documentation for added shaper profile parameters
Date: Mon, 22 Oct 2018 12:28:37 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F6602039CF2@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1540198001-127116-3-git-send-email-rosen.xu@intel.com>
> Update documentation for committed and peak parameters of shaper
> profile
>
> Signed-off-by: Rosen Xu <rosen.xu@intel.com>
> ---
> doc/guides/testpmd_app_ug/testpmd_funcs.rst | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Doc patch is ok just the commit heading is a but long
Running git log check: 47112
Headline too long:
doc/guides/testpmd_app_ug: update documentation for added shaper profile parameters
Reviewed-by: Marko Kovacevic <marko.kovacevic@intel.com>
next prev parent reply other threads:[~2018-10-22 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 10:34 [dpdk-dev] [PATCH] app/test-pmd: add and identify " Rosen Xu
2018-09-25 11:55 ` Singh, Jasvinder
2018-10-16 15:00 ` Dumitrescu, Cristian
2018-10-17 10:01 ` Xu, Rosen
2018-10-22 8:48 ` Xu, Rosen
2018-10-22 8:49 ` Xu, Rosen
2018-10-22 8:46 ` [dpdk-dev] [PATCH v2 0/2] Add " Rosen Xu
2018-10-22 8:46 ` [dpdk-dev] [PATCH v2 1/2] [PATCH v2 1/2] app/test-pmd: add " Rosen Xu
2018-10-22 8:46 ` [dpdk-dev] [PATCH v2 2/2] [PATCH v2 2/2] doc/guides/testpmd_app_ug: update documentation for added " Rosen Xu
2018-10-22 12:28 ` Kovacevic, Marko [this message]
2018-10-22 9:34 ` [dpdk-dev] [PATCH v2 0/2] Add and identify " Singh, Jasvinder
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=6DC05C7C5F25994B81B3F2F214251F6602039CF2@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=rosen.xu@intel.com \
--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).