From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH 2/4] test_plans/qos_api: fix doc build warning
Date: Fri, 1 Feb 2019 05:08:43 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA1FC59@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1548939888-104647-2-git-send-email-lijuan.tu@intel.com>
Applied, thanks
> -----Original Message-----
> From: Tu, Lijuan
> Sent: Thursday, January 31, 2019 9:05 PM
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>
> Subject: [PATCH 2/4] test_plans/qos_api: fix doc build warning
>
> Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
> ---
> test_plans/qos_api_test_plan.rst | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/test_plans/qos_api_test_plan.rst b/test_plans/qos_api_test_plan.rst
> index f89fdb3..f8a77d4 100644
> --- a/test_plans/qos_api_test_plan.rst
> +++ b/test_plans/qos_api_test_plan.rst
> @@ -40,6 +40,7 @@ The generic API for the Quality of Service (QoS) Traffic
> Management of Ethernet devices, which includes the following main features:
> hierarchical scheduling, traffic shaping, congestion management, packet
> marking.
> The TM setting commands are as following:
> +
> 1. Add the port traffic management private shaper profile::
>
> testpmd> add port tm node shaper profile (port_id) (shaper_profile_id) \ @@
> -82,7 +83,7 @@ Bind two ports to dpdk driver::
>
> ./usertools/dpdk-devbind.py -b igb_uio 05:00.0 05:00.1
>
> -Test Cases for I40e:
> +Test Cases for I40e:
> ====================
>
> Test Case: dcb 4 tc queue mapping
> @@ -266,7 +267,7 @@ Test Case: shaping for port
> verify shaping the traffic to 200Mbps(25MBps).
>
> Test Cases for ixgbe:
> -====================
> +=====================
>
> Test Case: dcb 4 tc queue mapping
> =================================
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-02-01 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:04 [dts] [PATCH 1/4] test_plans/dual_vlan: " Lijuan Tu
2019-01-31 13:04 ` [dts] [PATCH 2/4] test_plans/qos_api: " Lijuan Tu
2019-02-01 5:08 ` Tu, Lijuan [this message]
2019-01-31 13:04 ` [dts] [PATCH 3/4] test_plans/vlan_ethertype_config: " Lijuan Tu
2019-02-01 5:08 ` Tu, Lijuan
2019-01-31 13:04 ` [dts] [PATCH 4/4] test_plans/loopback_multi_paths_port_restart_performance: " Lijuan Tu
2019-02-01 5:09 ` Tu, Lijuan
2019-02-01 5:08 ` [dts] [PATCH 1/4] test_plans/dual_vlan: " Tu, Lijuan
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA1FC59@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@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).