test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhou, JunX W" <junx.w.zhou@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] hotplug/port_detach_attach_for_vhost_user_virtio_user:32 bites not support this case.
Date: Thu, 21 May 2020 06:53:17 +0000	[thread overview]
Message-ID: <EDA4914C4BAB5848BD29F696B5FE612D04433297@CDSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <1590041419-334355-1-git-send-email-junx.w.zhou@intel.com>

Tested-by:  Zhou, JunX W <junx.w.zhou@intel.com>

-----Original Message-----
From: Zhou, JunX W 
Sent: Thursday, May 21, 2020 2:10 PM
To: dts@dpdk.org
Cc: Zhou, JunX W <junx.w.zhou@intel.com>
Subject: [dts][PATCH V1] hotplug/port_detach_attach_for_vhost_user_virtio_user:32 bites not support this case.

From: Zhou jun <junx.w.zhou@intel.com>

change port_detach_attach_for_vhost_user_virtio_user's result to N/A.

Signed-off-by: Zhou jun <junx.w.zhou@intel.com>
---
 conf/test_case_checklist.json | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json index 3258e46..73eda68 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -3409,5 +3409,21 @@
             "Bug ID": "",
             "Comments": "NIC not support this case"
         }
+    ],
+    "port_detach_attach_for_vhost_user_virtio_user": [
+        {
+            "OS": [
+                "ALL"
+            ],
+            "NIC": [
+                "ALL"
+            ],
+            "Target": [
+                "i686-native-linuxapp-gcc",
+                "i686-native-linuxapp-icc"
+            ],
+            "Bug ID": "",
+            "Comments": "32 bites not support this case(memoory not enough)."
+        }
     ]
 }
--
1.8.3.1


  reply	other threads:[~2020-05-21  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  6:10 Zhou Jun
2020-05-21  6:53 ` Zhou, JunX W [this message]
2020-05-29  8:40 ` 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=EDA4914C4BAB5848BD29F696B5FE612D04433297@CDSMSX102.ccr.corp.intel.com \
    --to=junx.w.zhou@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).