From: Xie Wei <weix.xie@intel.com>
To: dts@dpdk.org
Cc: Xie Wei <weix.xie@intel.com>
Subject: [dts] [PATCH V2] conf/test_case_supportlist:this case only supported ixgbe
Date: Tue, 3 Mar 2020 14:19:31 +0800 [thread overview]
Message-ID: <1583216371-17830-1-git-send-email-weix.xie@intel.com> (raw)
Signed-off-by: Xie Wei <weix.xie@intel.com>
---
conf/test_case_supportlist.json | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/conf/test_case_supportlist.json b/conf/test_case_supportlist.json
index ffb2e6b..f716d5a 100644
--- a/conf/test_case_supportlist.json
+++ b/conf/test_case_supportlist.json
@@ -1717,5 +1717,20 @@
"Bug ID": "",
"Comments": "This case currently support for niantic"
}
+ ],
+ "ixgbe_vf_jumboframe": [
+ {
+ "OS": [
+ "ALL"
+ ],
+ "NIC": [
+ "niantic"
+ ],
+ "Target": [
+ "ALL"
+ ],
+ "Bug ID": "",
+ "Comments": "This case currently support for niantic"
+ }
]
}
--
2.17.2
next reply other threads:[~2020-03-03 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 6:19 Xie Wei [this message]
2020-03-03 7:35 ` 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=1583216371-17830-1-git-send-email-weix.xie@intel.com \
--to=weix.xie@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).