test suite reviews and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <rami.rosen@intel.com>
To: yong.liu@intel.com
Cc: dts@dpdk.org, Rami Rosen <rami.rosen@intel.com>
Subject: [dts] [PATCH] test_plans: fix typos in multiple pthread test plan.
Date: Sat, 19 Aug 2017 00:32:09 +0300	[thread overview]
Message-ID: <20170818213209.12610-1-rami.rosen@intel.com> (raw)

This patch fixes two trivial typos in multiple pthread test plan.

Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
 test_plans/multiple_pthread_test_plan.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/test_plans/multiple_pthread_test_plan.rst b/test_plans/multiple_pthread_test_plan.rst
index 4deeb1a778c7..8dad22d4a5ec 100644
--- a/test_plans/multiple_pthread_test_plan.rst
+++ b/test_plans/multiple_pthread_test_plan.rst
@@ -46,7 +46,7 @@ etc of a collection of processes. Now, it's focus on the CPU usage.
 Prerequisites
 -------------
 Support igb_uio driver, kernel is 3.11+. 
-Use "modeprobe uio" "modprobe igb_uio" and then 
+Use "modprobe uio" "modprobe igb_uio" and then
 use "./tools/dpdk_nic_bind.py --bind=igb_uio device_bus_id" to bind the ports.
 
 Assuming that an Intel's DPDK build has been set up and the testpmd
@@ -78,7 +78,7 @@ which means start 9 EAL thread::
 Test Case 1: Basic operation
 ----------------------------
 
-To run the application, start the testpmd with the lcoress all running with 
+To run the application, start the testpmd with the lcores all running with
 threads and also the unique core assigned, command as follows::
 
     ./x86_64-native-linuxapp-gcc/app/testpmd --lcores='0@8,(4-5)@9' -n 4 -- -i
-- 
2.11.0

             reply	other threads:[~2017-08-18 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 21:32 Rami Rosen [this message]
2017-08-22 11:24 ` 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=20170818213209.12610-1-rami.rosen@intel.com \
    --to=rami.rosen@intel.com \
    --cc=dts@dpdk.org \
    --cc=yong.liu@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).