test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Chen, LingliX" <linglix.chen@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Chen, LingliX" <linglix.chen@intel.com>
Subject: Re: [dts] [PATCH V1] conf/test_case_checklist:foxville not supoort case:txoffload_queue
Date: Sun, 28 Jun 2020 07:03:35 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC65A1C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200623083803.26525-1-linglix.chen@intel.com>

Foxville is a member of Fortville family, it is supposed to support  txoffload_queue

-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of chenlinglix
Sent: 2020年6月23日 16:38
To: dts@dpdk.org
Cc: Chen, LingliX <linglix.chen@intel.com>
Subject: [dts] [PATCH V1] conf/test_case_checklist:foxville not supoort case:txoffload_queue


 foxville not supoort case:txoffload_queue
Signed-off-by: chenlinglix <linglix.chen@intel.com>
---
 conf/test_case_checklist.json | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index 49fdb4c..b9ccc18 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -3496,5 +3496,20 @@
             "Bug ID": "",
             "Comments": "CVL not support DPDK PF + DPDK VF"
         }
+    ],
+    "txoffload_queue": [
+        {
+            "OS": [
+                "ALL"
+            ],
+            "NIC": [
+                "foxville"
+            ],
+            "Target": [
+                "ALL"
+            ],
+            "Bug ID": "",
+            "Comments": "the nic not support this case"
+        }
     ]
 }
--
1.8.3.1


      reply	other threads:[~2020-06-28  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  8:38 chenlinglix
2020-06-28  7:03 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC65A1C@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=linglix.chen@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).