From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id BD6B91B394 for ; Mon, 3 Dec 2018 04:33:26 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Dec 2018 19:33:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,308,1539673200"; d="scan'208";a="126368553" Received: from dts-maintain.sh.intel.com (HELO [10.67.119.110]) ([10.67.119.110]) by fmsmga001.fm.intel.com with ESMTP; 02 Dec 2018 19:33:24 -0800 To: Rami Rosen , dts@dpdk.org References: <20181201072346.3925-1-ramirose@gmail.com> From: Lijuan Tu Message-ID: Date: Mon, 3 Dec 2018 20:01:13 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20181201072346.3925-1-ramirose@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Subject: Re: [dts] [PATCH] test_plans: remove double "to" in all test plans. X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Dec 2018 03:33:27 -0000 Glad to see your more and more contribution. Applied, thanks On 2018年12月01日 15:23, Rami Rosen wrote: > This patch removes usage of double "to" in all test plans. > > Signed-off-by: Rami Rosen > --- > test_plans/NICStatistics_test_plan.rst | 2 +- > test_plans/blacklist_test_plan.rst | 2 +- > test_plans/checksum_offload_test_plan.rst | 2 +- > test_plans/cmdline_test_plan.rst | 2 +- > test_plans/dual_vlan_test_plan.rst | 2 +- > test_plans/dynamic_config_test_plan.rst | 2 +- > test_plans/fdir_test_plan.rst | 4 ++-- > test_plans/ieee1588_test_plan.rst | 2 +- > test_plans/ipfrag_test_plan.rst | 2 +- > test_plans/ipv4_reassembly_test_plan.rst | 2 +- > test_plans/jumboframes_test_plan.rst | 2 +- > test_plans/kni_test_plan.rst | 2 +- > test_plans/l2fwd_test_plan.rst | 2 +- > test_plans/l3fwd_em_test_plan.rst | 2 +- > test_plans/l3fwd_test_plan.rst | 2 +- > test_plans/link_flowctrl_test_plan.rst | 2 +- > test_plans/link_status_interrupt_test_plan.rst | 2 +- > test_plans/mac_filter_test_plan.rst | 2 +- > test_plans/multiprocess_test_plan.rst | 2 +- > test_plans/pmd_test_plan.rst | 2 +- > test_plans/shutdown_api_test_plan.rst | 2 +- > test_plans/timer_test_plan.rst | 2 +- > test_plans/vf_offload_test_plan.rst | 2 +- > 23 files changed, 24 insertions(+), 24 deletions(-) > > diff --git a/test_plans/NICStatistics_test_plan.rst b/test_plans/NICStatistics_test_plan.rst > index 86bd8d1..cfae706 100644 > --- a/test_plans/NICStatistics_test_plan.rst > +++ b/test_plans/NICStatistics_test_plan.rst > @@ -69,7 +69,7 @@ will only be done on the userland application, as the tool requires a > Linux environment to be running in order to be used. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/blacklist_test_plan.rst b/test_plans/blacklist_test_plan.rst > index bc23c0d..02b3c2f 100644 > --- a/test_plans/blacklist_test_plan.rst > +++ b/test_plans/blacklist_test_plan.rst > @@ -40,7 +40,7 @@ Prerequisites > Board with at least 2 DPDK supported NICs attached. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/checksum_offload_test_plan.rst b/test_plans/checksum_offload_test_plan.rst > index 9ebbc02..710b98a 100644 > --- a/test_plans/checksum_offload_test_plan.rst > +++ b/test_plans/checksum_offload_test_plan.rst > @@ -81,7 +81,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/cmdline_test_plan.rst b/test_plans/cmdline_test_plan.rst > index 0d957c1..d149999 100644 > --- a/test_plans/cmdline_test_plan.rst > +++ b/test_plans/cmdline_test_plan.rst > @@ -59,7 +59,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/dual_vlan_test_plan.rst b/test_plans/dual_vlan_test_plan.rst > index af476e2..f828c18 100644 > --- a/test_plans/dual_vlan_test_plan.rst > +++ b/test_plans/dual_vlan_test_plan.rst > @@ -46,7 +46,7 @@ Prerequisites > In this feature, Only 82576 and 82599 are supported. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/dynamic_config_test_plan.rst b/test_plans/dynamic_config_test_plan.rst > index 8b9e660..4b6b1c7 100644 > --- a/test_plans/dynamic_config_test_plan.rst > +++ b/test_plans/dynamic_config_test_plan.rst > @@ -56,7 +56,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/fdir_test_plan.rst b/test_plans/fdir_test_plan.rst > index 9575ba0..dee03c3 100644 > --- a/test_plans/fdir_test_plan.rst > +++ b/test_plans/fdir_test_plan.rst > @@ -65,7 +65,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > @@ -475,7 +475,7 @@ filter and check that there is a match:: > Test case: FDir filter masks > ============================ > > -This section tests the functionality of the setting FDir masks to to affect > +This section tests the functionality of the setting FDir masks to affect > which fields, or parts of fields are used in the matching process. Note that > setting up a mask resets all the FDir filters, so the ``testpmd`` application > does not have to be relaunched for each sub-case. > diff --git a/test_plans/ieee1588_test_plan.rst b/test_plans/ieee1588_test_plan.rst > index 842cb03..29e6176 100644 > --- a/test_plans/ieee1588_test_plan.rst > +++ b/test_plans/ieee1588_test_plan.rst > @@ -74,7 +74,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/ipfrag_test_plan.rst b/test_plans/ipfrag_test_plan.rst > index b7459f7..9c0afed 100644 > --- a/test_plans/ipfrag_test_plan.rst > +++ b/test_plans/ipfrag_test_plan.rst > @@ -79,7 +79,7 @@ Prerequisites > 4. Software application requirements > > 5. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > - using vfio, use the following commands to to load the vfio driver and bind it > + using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/ipv4_reassembly_test_plan.rst b/test_plans/ipv4_reassembly_test_plan.rst > index 1b15b5d..686584d 100644 > --- a/test_plans/ipv4_reassembly_test_plan.rst > +++ b/test_plans/ipv4_reassembly_test_plan.rst > @@ -46,7 +46,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/jumboframes_test_plan.rst b/test_plans/jumboframes_test_plan.rst > index 0edf6d2..9c3dd87 100644 > --- a/test_plans/jumboframes_test_plan.rst > +++ b/test_plans/jumboframes_test_plan.rst > @@ -43,7 +43,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/kni_test_plan.rst b/test_plans/kni_test_plan.rst > index fc10f5e..0c5b2e0 100644 > --- a/test_plans/kni_test_plan.rst > +++ b/test_plans/kni_test_plan.rst > @@ -100,7 +100,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/l2fwd_test_plan.rst b/test_plans/l2fwd_test_plan.rst > index f459633..6bbed76 100644 > --- a/test_plans/l2fwd_test_plan.rst > +++ b/test_plans/l2fwd_test_plan.rst > @@ -64,7 +64,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/l3fwd_em_test_plan.rst b/test_plans/l3fwd_em_test_plan.rst > index d6ecd14..7f4fefd 100644 > --- a/test_plans/l3fwd_em_test_plan.rst > +++ b/test_plans/l3fwd_em_test_plan.rst > @@ -77,7 +77,7 @@ Prerequisites > 4. Software application requirements > > 5. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > - using vfio, use the following commands to to load the vfio driver and bind it > + using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/l3fwd_test_plan.rst b/test_plans/l3fwd_test_plan.rst > index 0f90345..ceb449f 100644 > --- a/test_plans/l3fwd_test_plan.rst > +++ b/test_plans/l3fwd_test_plan.rst > @@ -77,7 +77,7 @@ Prerequisites > 4. Software application requirements > > 5. If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > - using vfio, use the following commands to to load the vfio driver and bind it > + using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/link_flowctrl_test_plan.rst b/test_plans/link_flowctrl_test_plan.rst > index b041799..d028e67 100644 > --- a/test_plans/link_flowctrl_test_plan.rst > +++ b/test_plans/link_flowctrl_test_plan.rst > @@ -74,7 +74,7 @@ The -n command is used to select the number of memory channels. > It should match the number of memory channels on that setup. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/link_status_interrupt_test_plan.rst b/test_plans/link_status_interrupt_test_plan.rst > index a740684..32dea9a 100644 > --- a/test_plans/link_status_interrupt_test_plan.rst > +++ b/test_plans/link_status_interrupt_test_plan.rst > @@ -64,7 +64,7 @@ Prerequisites > ============= > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/mac_filter_test_plan.rst b/test_plans/mac_filter_test_plan.rst > index 26e57cc..1335e9f 100644 > --- a/test_plans/mac_filter_test_plan.rst > +++ b/test_plans/mac_filter_test_plan.rst > @@ -35,7 +35,7 @@ Whitelisting Tests > ================== > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/multiprocess_test_plan.rst b/test_plans/multiprocess_test_plan.rst > index ae0dd85..8598048 100644 > --- a/test_plans/multiprocess_test_plan.rst > +++ b/test_plans/multiprocess_test_plan.rst > @@ -51,7 +51,7 @@ Prerequisites > ------------- > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/pmd_test_plan.rst b/test_plans/pmd_test_plan.rst > index f3b4b90..5d2c154 100644 > --- a/test_plans/pmd_test_plan.rst > +++ b/test_plans/pmd_test_plan.rst > @@ -69,7 +69,7 @@ will only be done on the userland application, as the tool requires a > Linux environment to be running in order to be used. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/shutdown_api_test_plan.rst b/test_plans/shutdown_api_test_plan.rst > index 86c8bbc..2d549e8 100644 > --- a/test_plans/shutdown_api_test_plan.rst > +++ b/test_plans/shutdown_api_test_plan.rst > @@ -50,7 +50,7 @@ Prerequisites > ------------- > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/timer_test_plan.rst b/test_plans/timer_test_plan.rst > index cccbccf..91e83a8 100644 > --- a/test_plans/timer_test_plan.rst > +++ b/test_plans/timer_test_plan.rst > @@ -39,7 +39,7 @@ program print some messages from different lcores regularly, > demonstrating how to use timers. > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio > diff --git a/test_plans/vf_offload_test_plan.rst b/test_plans/vf_offload_test_plan.rst > index ab8dbd1..59c54c4 100644 > --- a/test_plans/vf_offload_test_plan.rst > +++ b/test_plans/vf_offload_test_plan.rst > @@ -39,7 +39,7 @@ Prerequisites for checksum offload > ================================== > > If using vfio the kernel must be >= 3.6+ and VT-d must be enabled in bios.When > -using vfio, use the following commands to to load the vfio driver and bind it > +using vfio, use the following commands to load the vfio driver and bind it > to the device under test:: > > modprobe vfio