From: Rami Rosen <rami.rosen@intel.com>
To: dts@dpdk.org
Cc: Rami Rosen <rami.rosen@intel.com>
Subject: [dts] [PATCH] test_plans: nvgre - fix typos.
Date: Fri, 12 Aug 2016 19:09:06 +0300 [thread overview]
Message-ID: <1471018146-32385-1-git-send-email-rami.rosen@intel.com> (raw)
This patch fixes trivial typos in test_plans/vxlan_test_plan.rst.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
test_plans/nvgre_test_plan.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/test_plans/nvgre_test_plan.rst b/test_plans/nvgre_test_plan.rst
index 4e4a9f4..061682b 100644
--- a/test_plans/nvgre_test_plan.rst
+++ b/test_plans/nvgre_test_plan.rst
@@ -184,15 +184,15 @@ Add NVGRE filter as table listed first::
Validte the filter command with wrong parameter::
-Add Clould filter with invalid Mac address "00:00:00:00:01" will be failed.
+Add Cloud filter with invalid Mac address "00:00:00:00:01" will be failed.
-Add Clould filter with invalid ip address "192.168.1.256" will be failed.
+Add Cloud filter with invalid ip address "192.168.1.256" will be failed.
-Add Clould filter with invalid vlan "4097" will be failed.
+Add Cloud filter with invalid vlan "4097" will be failed.
-Add Clould filter with invalid vni "16777216" will be failed.
+Add Cloud filter with invalid vni "16777216" will be failed.
-Add Clould filter with invalid queue id "64" will be failed.
+Add Cloud filter with invalid queue id "64" will be failed.
Test Case: NVGRE IPv6 Filter
========================
--
2.5.5
next reply other threads:[~2016-08-12 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 16:09 Rami Rosen [this message]
2016-08-15 2:31 ` Liu, Yong
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=1471018146-32385-1-git-send-email-rami.rosen@intel.com \
--to=rami.rosen@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).