From: "Mo, YufengX" <yufengx.mo@intel.com>
To: dts@dpdk.org
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V3 2/2] [examples/flow_classify]: add flow_classify_test_plan label
Date: Tue, 18 Jun 2019 15:15:06 +0800 [thread overview]
Message-ID: <20190618071506.14844-3-yufengx.mo@intel.com> (raw)
In-Reply-To: <20190618071506.14844-1-yufengx.mo@intel.com>
From: yufengmx <yufengx.mo@intel.com>
add flow_classify_test_plan label
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
test_plans/index.rst | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/test_plans/index.rst b/test_plans/index.rst
index 712d094..52d4e55 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -130,6 +130,10 @@ The following are the test plans for the DPDK DTS automated test system.
loadbalancer_test_plan
loopback_multi_queues_test_plan
telemetry_test_plan
+ compressdev_isal_pmd_test_plan
+ compressdev_qat_pmd_test_plan
+ compressdev_zlib_pmd_test_plan
+ enable_package_download_in_ice_driver_test_plan
veb_switch_test_plan
vf_daemon_test_plan
@@ -152,6 +156,8 @@ The following are the test plans for the DPDK DTS automated test system.
vhost_user_live_migration_test_plan
vm_power_manager_test_plan
vmdq_test_plan
+ vf_l3fwd_test_plan
+ softnic_test_plan
virtio_1.0_test_plan
vhost_enqueue_interrupt_test_plan
@@ -163,6 +169,21 @@ The following are the test plans for the DPDK DTS automated test system.
virtio_perf_cryptodev_func_test_plan
vm2vm_virtio_net_perf_test_plan
vm2vm_virtio_pmd_test_plan
+ dpdk_gro_lib_test_plan
+ dpdk_gso_lib_test_plan
+ vhost_dequeue_zero_copy_test_plan
+ vxlan_gpe_support_in_i40e_test_plan
+ pvp_diff_qemu_version_test_plan
+ pvp_qemu_zero_copy_test_plan
+ pvp_share_lib_test_plan
+ pvp_vhost_user_built_in_net_driver_test_plan
+ pvp_virtio_user_2M_hugepages_test_plan
+ pvp_virtio_user_multi_queues_test_plan
+ vhost_gro_test_plan
+ virtio_unit_cryptodev_func_test_plan
+ virtio_user_for_container_networking_test_plan
+ eventdev_perf_test_plan
+ eventdev_pipeline_perf_test_plan
unit_tests_cmdline_test_plan
unit_tests_crc_test_plan
@@ -195,3 +216,4 @@ The following are the test plans for the DPDK DTS automated test system.
distributor_test_plan
efd_test_plan
example_build_test_plan
+ flow_classify_test_plan
--
1.9.3
next prev parent reply other threads:[~2019-06-18 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 7:15 [dts] [PATCH V3 0/2] [examples/flow_classify]: upload test plan Mo, YufengX
2019-06-18 7:15 ` [dts] [PATCH V3 1/2] " Mo, YufengX
2019-06-18 7:15 ` Mo, YufengX [this message]
2019-06-18 8:59 [dts] [PATCH V3 0/2] " yufengmx
2019-06-18 8:59 ` [dts] [PATCH V3 2/2] [examples/flow_classify]: add flow_classify_test_plan label yufengmx
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=20190618071506.14844-3-yufengx.mo@intel.com \
--to=yufengx.mo@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).