From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH 3/4] test_plans/vlan_ethertype_config: fix doc build warning
Date: Fri, 1 Feb 2019 05:08:49 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA1FC61@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1548939888-104647-3-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 3/4] test_plans/vlan_ethertype_config: fix doc build warning
>
> Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
> ---
> test_plans/vlan_ethertype_config_test_plan.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/test_plans/vlan_ethertype_config_test_plan.rst
> b/test_plans/vlan_ethertype_config_test_plan.rst
> index 81b7d9b..7096614 100644
> --- a/test_plans/vlan_ethertype_config_test_plan.rst
> +++ b/test_plans/vlan_ethertype_config_test_plan.rst
> @@ -124,7 +124,7 @@ Test Case 3: test adding VLAN Tag Identifier with
> changing VLAN TPID
> Verify that the VLAN packet cannot be received in port ``B``.
>
> Test Case 4: test VLAN header stripping with changing VLAN TPID -
> ==============================================================
> +===============================================================
>
> 1. start testpmd, setup vlan filter off, vlan strip on, start in mac forwarding
> mode::
>
> @@ -142,7 +142,7 @@ Test Case 4: test VLAN header stripping with changing
> VLAN TPID
> testpmd> vlan set outer tpid 0xA100 0
>
> 4. Send 1 packet with VLAN TPID 0xA100 and VLAN Tag 16 on port ``A``.
> -Verify that packet received in port ``B`` without VLAN Tag Identifier
> + Verify that packet received in port ``B`` without VLAN Tag Identifier
>
> 5. Disable vlan header stripping on port ``0``::
>
> --
> 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
2019-01-31 13:04 ` [dts] [PATCH 3/4] test_plans/vlan_ethertype_config: " Lijuan Tu
2019-02-01 5:08 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BA1FC61@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).