test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Yao, BingX Y" <bingx.y.yao@intel.com>
To: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/fdir add not support nic for cases
Date: Wed, 30 Jan 2019 02:45:00 +0000	[thread overview]
Message-ID: <95BCD24840F32441BEA74E0F8A31839E04EF128E@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1548812066-42807-1-git-send-email-wenhuix.zhu@intel.com>


Tested-by: yaobing <bingx.y.yao@intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhuwenhui
Sent: Wednesday, January 30, 2019 9:34 AM
To: dts@dpdk.org
Cc: Zhu, WenhuiX <wenhuix.zhu@intel.com>
Subject: [dts] [PATCH V1] tests/fdir add not support nic for cases

add not support nics to fdir_flexword_drop_ipv6 and fdir_noflexword_drop_ipv6

Signed-off-by: zhuwenhui <wenhuix.zhu@intel.com>
---
 conf/test_case_checklist.json | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index eeb4321..a1aa90b 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -586,6 +586,7 @@
                 "ironpond",
                 "springfountain",
                 "twinpond",
+		"niantic",
                 "cavium_a034",
                 "cavium_0011"
             ],
@@ -726,6 +727,7 @@
                 "ironpond",
                 "springfountain",
                 "twinpond",
+		"niantic",
                 "cavium_a034",
                 "cavium_0011"
             ],
--
2.17.2

  reply	other threads:[~2019-01-30  2:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  1:34 zhuwenhui
2019-01-30  2:45 ` Yao, BingX Y [this message]
2019-01-30  6:53 ` 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=95BCD24840F32441BEA74E0F8A31839E04EF128E@shsmsx102.ccr.corp.intel.com \
    --to=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenhuix.zhu@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).