From: Rami Rosen <ramirose@gmail.com>
To: dts@dpdk.org
Cc: yanjie.xu@intel.com, Rami Rosen <ramirose@gmail.com>
Subject: [dts] [PATCH] test_plans/telemetry: fix a typo
Date: Thu, 18 Apr 2019 07:36:51 +0300 [thread overview]
Message-ID: <1555562211-71315-1-git-send-email-ramirose@gmail.com> (raw)
This patch fixes the following typo in telemetry test plan:
and very => and verify
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
test_plans/telemetry_test_plan.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/test_plans/telemetry_test_plan.rst b/test_plans/telemetry_test_plan.rst
index 8c8898e..1085fd5 100644
--- a/test_plans/telemetry_test_plan.rst
+++ b/test_plans/telemetry_test_plan.rst
@@ -118,7 +118,7 @@ Test case: Stats of 2 ports for testpmd and telemetry with same type nic
python ./usertools/telemetry_client.py
enter 1/2/ :
-4.check and very any error show on testpmd
+4.check and verify any error show on testpmd
5.set rx/tx configration by testpmd
@@ -149,7 +149,7 @@ Test case: Stats of 2 ports for testpmd and telemetry with different type nic
python ./usertools/telemetry_client.py
enter 1/2/ :
-4.check and very any error show on testpmd
+4.check and verify any error show on testpmd
5.set rx/tx configration by testpmd
@@ -180,7 +180,7 @@ Test case: Stats of 4 ports for testpmd and telemetry with same type nic
python ./usertools/telemetry_client.py
enter 1/2/
-4.check and very any error show on testpmd
+4.check and verify any error show on testpmd
5.set rx/tx configration by testpmd
@@ -211,7 +211,7 @@ Test case: Stats of 4 ports for testpmd and telemetry with different type nic
python ./usertools/telemetry_client.py
enter 1/2/ :
-4.check and very any error show on testpmd
+4.check and verify any error show on testpmd
5.set rx/tx configration by testpmd
--
1.8.3.1
next reply other threads:[~2019-04-18 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 4:36 Rami Rosen [this message]
2019-04-18 23:57 ` 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=1555562211-71315-1-git-send-email-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dts@dpdk.org \
--cc=yanjie.xu@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).