test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V1] conf/supportlist: add fortpark_TLV to uni_pkt cases
Date: Wed, 5 Jun 2019 02:14:01 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAA051E@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1559191626-117070-1-git-send-email-wenjiex.a.li@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Thursday, May 30, 2019 12:47 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V1] conf/supportlist: add fortpark_TLV to uni_pkt cases
> 
> Below cases in tests/uni_pkt can support fortpark_TLV, update supportlist.
> l2pkt_detect
> IPv6_in_IPv4_tunnel
> IP_in_IPv6_tunnel
> NVGRE_tunnel
> NVGRE_in_IPv6_tunnel
> GRE_tunnel
> Vxlan_tunnel
> 
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
>  conf/test_case_supportlist.json | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json
> index 436bbb7..04e90be 100644
> --- a/conf/test_case_supportlist.json
> +++ b/conf/test_case_supportlist.json
> @@ -129,6 +129,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -147,6 +148,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -186,6 +188,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -204,6 +207,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -222,6 +226,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -240,6 +245,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single", @@ -258,6 +264,7 @@
>                  "ALL"
>              ],
>              "NIC": [
> +                "forrpark_TLV",
>                  "fortville_eagle",
>                  "fortville_spirit",
>                  "fortville_spirit_single",
> --
> 2.17.2


      reply	other threads:[~2019-06-05  2:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  4:47 Wenjie Li
2019-06-05  2:14 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BAA051E@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenjiex.a.li@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).