[dts] [PATCH V2] test_plans:fix build warning

[Tu, Lijuan]

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces at dpdk.org] On Behalf Of Wenjie Li
> Sent: Monday, September 23, 2019 11:06 AM
> To: dts at dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li at intel.com>
> Subject: [dts] [PATCH V2] test_plans:fix build warning
> 
> fix build warning
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li at intel.com>
> V2: fix "1 line adds whitespace errors."
> 0001-test_plans-fix-build-warning.patch:26: trailing whitespace.
>    (b) Windriver TS 2 or CentOS 7 operating systems
> warning: 1 line adds whitespace errors.
> 
> 
> ---
>  test_plans/bbdev_test_plan.rst     |  6 +++++-
>  test_plans/index.rst               |  7 ++++++-
>  test_plans/sriov_kvm_test_plan.rst | 14 ++++++++++----
>  3 files changed, 21 insertions(+), 6 deletions(-)
> 
> diff --git a/test_plans/bbdev_test_plan.rst b/test_plans/bbdev_test_plan.rst
> index 800e7f6..7fa0e2a 100644
> --- a/test_plans/bbdev_test_plan.rst
> +++ b/test_plans/bbdev_test_plan.rst
> @@ -67,12 +67,14 @@ Prerequisites
>  =============
> 
>  1. OS and Hardware
> +
>     (a) An AVX2 supporting machine
> -   (b) Windriver TS 2 or CentOS 7 operating systems
> +   (b) Windriver TS 2 or CentOS 7 operating systems
>         (Fedora 25 and Ubuntu 16.04 is ok.)
>     (c) Intel ICC compiler installed
> 
>  2. FlexRAN SDK Libraries
> +
>     To build DPDK with the *turbo_sw* PMD the user is required to download
>     the export controlled ``FlexRAN SDK`` Libraries.
>     An account at Intel Resource Design Center needs to be registered from
> @@ -84,6 +86,7 @@ Prerequisites
>     You can refer to the file dpdk/doc/guides/bbdevs/turbo_sw.rst.
> 
>  3. PMD setting
> +
>     Current BBDEV framework is en-suited with two vdev PMD drivers:
>     null and turbo_sw.
>     1) Null PMD is similar to cryptodev Null PMD, which is an empty driver to
> @@ -101,6 +104,7 @@ Prerequisites
>     They are both located in the build configuration file ``common_base``.
> 
>  4. Test tool
> +
>     A test suite for BBDEV is packaged with the framework to ease the
>     validation needs for various functions and use cases.
>     The tool to use for validation and testing is called: test-bbdev, diff --git
> a/test_plans/index.rst b/test_plans/index.rst index 28f5a69..e15823e 100644
> --- a/test_plans/index.rst
> +++ b/test_plans/index.rst
> @@ -133,6 +133,7 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      compressdev_qat_pmd_test_plan
>      compressdev_zlib_pmd_test_plan
>      enable_package_download_in_ice_driver_test_plan
> +    multicast_test_plan
> 
>      veb_switch_test_plan
>      vf_daemon_test_plan
> @@ -151,7 +152,6 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      vhost_multi_queue_qemu_test_plan
>      vhost_pmd_xstats_test_plan
>      vhost_qemu_mtu_test_plan
> -    vhost_tso_test_plan
>      vhost_user_live_migration_test_plan
>      vm_power_manager_test_plan
>      vmdq_test_plan
> @@ -230,3 +230,8 @@ The following are the test plans for the DPDK DTS
> automated test system.
>      iavf_test_plan
>      packet_capture_test_plan
>      packet_ordering_test_plan
> +    bbdev_test_plan
> +    performance_thread_test_plan
> +
> +    fips_cryptodev_test_plan
> +    flow_filtering_test_plan
> \ No newline at end of file
> diff --git a/test_plans/sriov_kvm_test_plan.rst
> b/test_plans/sriov_kvm_test_plan.rst
> index f22b2ed..1b84f78 100644
> --- a/test_plans/sriov_kvm_test_plan.rst
> +++ b/test_plans/sriov_kvm_test_plan.rst
> @@ -135,7 +135,7 @@ Send 10 packets with VF0 mac address and make
> sure the packets will be  forwarded by VF1.
> 
>  Test Case2: Mirror Traffic between 2VMs with Pool up mirroring -
> ===========================================================
> +==============================================================
> 
>  Set up common 2VM prerequisites.
> 
> @@ -216,7 +216,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 0
> 
>  Test Case6: Mirror Traffic between 2VMs with Vlan mirroring -
> ==========================================================
> +===========================================================
> 
>  Set up common 2VM prerequisites.
> 
> @@ -237,7 +237,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 0
> 
>  Test Case7: Mirror Traffic between 2VMs with up link mirroring & down link
> mirroring -
> ================================================================
> ==================
> +===============================================================
> ========
> +=============
> 
>  Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
> 
> @@ -247,9 +247,12 @@ Run testpmd on VM0 and VM1 and start traffic
> forward on the VM hosts::
>  When mirroring only between two Vfs, pool up (or down) mirroring and up
> (or down) link mirroring lead  to the same behavior, so we randomly choose
> one way to mirror in both up and down directions.
>  up link mirroring as below:
> +
>     1. Pool up mirroring (Case 2)
>     2. Uplink port mirroring(Case 4)
> +
>  down link mirroring as below:
> +
>     1. Pool down mirroring(Fortville only, Case 3)
>     2. Downlink port mirroring(Case 5)
> 
> @@ -274,7 +277,7 @@ After test need reset mirror rule::
>      PF testpmd-> reset port 0 mirror-rule 1
> 
>  Test Case8: Mirror Traffic between 2VMs with Vlan & with up link mirroring
> & down link mirroring -
> ================================================================
> =============================
> +===============================================================
> ========
> +=========================
> 
>  Run testpmd on VM0 and VM1 and start traffic forward on the VM hosts::
> 
> @@ -284,9 +287,12 @@ Run testpmd on VM0 and VM1 and start traffic
> forward on the VM hosts::
>  When mirroring only between two Vfs, pool up (or down) mirroring and up
> (or down) link mirroring lead  to the same behavior, so we randomly choose
> one way to mirror in both up and down directions.
>  up link mirroring as below:
> +
>     1. Pool up mirroring (Case 2)
>     2. Uplink port mirroring(Case 4)
> +
>  down link mirroring as below:
> +
>     1. Pool down mirroring(Fortville only, Case 3)
>     2. Downlink port mirroring(Case 5)
> 
> --
> 2.17.2