From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/3] examples/qos_sched: documentation update
Date: Mon, 4 Nov 2019 10:29:41 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E95A7AE@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20191029131942.50298-2-jasvinder.singh@intel.com>
> -----Original Message-----
> From: Singh, Jasvinder <jasvinder.singh@intel.com>
> Sent: Tuesday, October 29, 2019 1:20 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Subject: [PATCH 2/3] examples/qos_sched: documentation update
>
> Update documentation according to the changes made to qos sample
> app.
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> ---
> doc/guides/sample_app_ug/qos_scheduler.rst | 92
> +++++++++++++++++++---
> 1 file changed, 81 insertions(+), 11 deletions(-)
>
> diff --git a/doc/guides/sample_app_ug/qos_scheduler.rst
> b/doc/guides/sample_app_ug/qos_scheduler.rst
> index cdd29d90c..b5010657a 100644
> --- a/doc/guides/sample_app_ug/qos_scheduler.rst
> +++ b/doc/guides/sample_app_ug/qos_scheduler.rst
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2019-11-04 10:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 13:19 [dpdk-dev] [PATCH 1/3] sched: " Jasvinder Singh
2019-10-29 13:19 ` [dpdk-dev] [PATCH 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-04 10:29 ` Dumitrescu, Cristian [this message]
2019-10-29 13:19 ` [dpdk-dev] [PATCH 3/3] examples/ip_pipeline: " Jasvinder Singh
2019-11-04 10:29 ` Dumitrescu, Cristian
2019-11-04 10:30 ` [dpdk-dev] [PATCH 1/3] sched: " Dumitrescu, Cristian
2019-11-26 8:47 ` Thomas Monjalon
2019-11-26 9:16 ` Thomas Monjalon
2019-11-26 9:55 ` Singh, Jasvinder
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 " Jasvinder Singh
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 3/3] examples/ip_pipeline: " Jasvinder Singh
2019-11-26 15:22 ` [dpdk-dev] [PATCH v2 1/3] sched: " Thomas Monjalon
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=3EB4FA525960D640B5BDFFD6A3D891268E95A7AE@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).