test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Tu, LijuanX A" <lijuanx.a.tu@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>,
	"Pei, Yulong" <yulong.pei@intel.com>
Cc: "Tu, LijuanX A" <lijuanx.a.tu@intel.com>
Subject: Re: [dts] [PATCH V1 1/2] test_plans/vlan_ethertype_config_test_plan:	using outer instead inner to config single vlan tpid
Date: Mon, 27 Mar 2017 01:17:32 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62D97D9D@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1490336754-106860-1-git-send-email-lijuanx.a.tu@intel.com>

Hi Jijuan,
Please give the reason why change from outer to inter in your commit log.

Thanks,
Marvin

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Lijuan Tu
> Sent: Friday, March 24, 2017 2:26 PM
> To: dts@dpdk.org; Pei, Yulong <yulong.pei@intel.com>
> Cc: Tu, LijuanX A <lijuanx.a.tu@intel.com>
> Subject: [dts] [PATCH V1 1/2] test_plans/vlan_ethertype_config_test_plan:
> using outer instead inner to config single vlan tpid
> 
> Signed-off-by: Lijuan Tu <lijuanx.a.tu@intel.com>
> ---
>  test_plans/vlan_ethertype_config_test_plan.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/test_plans/vlan_ethertype_config_test_plan.rst
> b/test_plans/vlan_ethertype_config_test_plan.rst
> index 27dbda7..9d565e7 100644
> --- a/test_plans/vlan_ethertype_config_test_plan.rst
> +++ b/test_plans/vlan_ethertype_config_test_plan.rst
> @@ -65,7 +65,7 @@ testpmd> start
> 
>  2) change VLAN TPIDs to 0xA100,
> 
> -testpmd> vlan set inner tpid 0xA100 0
> +testpmd> vlan set outer tpid 0xA100 0
> 
>  3) send a packet with VLAN TPIDs = 0xA100, verify it can be recognized as
> vlan packet.
> 
> @@ -108,7 +108,7 @@ Verify that the VLAN packet can be received in port
> ``B`` and TPID is 0x8100
> 
>  4) Change VLAN TPID to 0xA100 on port ``0``
> 
> -testpmd> vlan set inner tpid 0xA100 0
> +testpmd> vlan set outer tpid 0xA100 0
> 
>  5) send 1 packet with VLAN TPID 0xA100 and VLAN Tag 16 on port ``A``,
>  Verify that the VLAN packet can be received in port ``B`` and TPID is
> 0xA100
> @@ -136,7 +136,7 @@ Verify that packet received in port ``B`` without VLAN
> Tag Identifier
> 
>  3) Change VLAN TPID to 0xA100 on port ``0``
> 
> -testpmd> vlan set inner tpid 0xA100 0
> +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
> @@ -169,7 +169,7 @@ Verify that packet received in port ``B`` with VLAN
> Tag Identifier 16 and TPID i
> 
>  4) Change VLAN TPID to 0xA100 on port ``1``
> 
> -testpmd> vlan set inner tpid 0xA100 1
> +testpmd> vlan set outer tpid 0xA100 1
> 
>  5)send 1 packet without VLAN Tag Identifier on port ``A``,
>  Verify that packet received in port ``B`` with VLAN Tag Identifier 16 and
> TPID is 0xA100.
> --
> 1.9.3

      parent reply	other threads:[~2017-03-27  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  6:25 Lijuan Tu
2017-03-24  6:25 ` [dts] [PATCH V1 2/2] tests/vlan_ethertype_config: add script Lijuan Tu
2017-03-27  1:17 ` Liu, Yong [this message]

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=86228AFD5BCD8E4EBFD2B90117B5E81E62D97D9D@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuanx.a.tu@intel.com \
    --cc=yulong.pei@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).