test suite reviews and discussions
 help / color / mirror / Atom feed
From: Xingguang He <xingguang.he@intel.com>
To: dts@dpdk.org
Cc: Xingguang He <xingguang.he@intel.com>
Subject: [dts][PATCH V2 1/3] test_plans/index: modify the test plan name from vm2vm_virtio_net_dsa to vm2vm_virtio_net_perf_dsa
Date: Wed,  7 Sep 2022 03:05:05 +0000	[thread overview]
Message-ID: <20220907030507.1186225-2-xingguang.he@intel.com> (raw)
In-Reply-To: <20220907030507.1186225-1-xingguang.he@intel.com>

Modify the test plan name from vm2vm_virtio_net_dsa to
vm2vm_virtio_net_perf_dsa.

Signed-off-by: Xingguang He <xingguang.he@intel.com>
---
 test_plans/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test_plans/index.rst b/test_plans/index.rst
index 2d797b6d..43c0fd29 100644
--- a/test_plans/index.rst
+++ b/test_plans/index.rst
@@ -208,7 +208,7 @@ The following are the test plans for the DPDK DTS automated test system.
     virtio_smoke_test_plan
     vm2vm_virtio_net_perf_test_plan
     vm2vm_virtio_net_perf_cbdma_test_plan
-    vm2vm_virtio_net_dsa_test_plan
+    vm2vm_virtio_net_perf_dsa_test_plan
     vm2vm_virtio_pmd_test_plan
     vm2vm_virtio_pmd_cbdma_test_plan
     dpdk_gro_lib_test_plan
-- 
2.25.1


  reply	other threads:[~2022-09-07  3:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  3:05 [dts][PATCH V2 0/3] modify vm2vm_virtio_net_perf_dsa_test_plan Xingguang He
2022-09-07  3:05 ` Xingguang He [this message]
2022-09-07  3:05 ` [dts][PATCH V2 2/3] test_plans/vm2vm_virtio_net_dsa_test_plan: delete and modify test plan name from vm2vm_virtio_net_dsa to vm2vm_virtio_net_perf_dsa Xingguang He
2022-09-07  3:05 ` [dts][PATCH V2 3/3] test_plans/vm2vm_virtio_net_perf_dsa_test_plan: modify test plan to test vhost async dequeue Xingguang He
2022-10-10  3:10   ` lijuan.tu

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=20220907030507.1186225-2-xingguang.he@intel.com \
    --to=xingguang.he@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).