DPDK patches and discussions
 help / color / mirror / Atom feed
From: Roy Franz <rfranz@cavium.com>
To: dev@dpdk.org
Cc: Roy Franz <roy.franz@cavium.com>
Subject: [dpdk-dev] [PATCH 2/2] doc: Fix typo
Date: Fri,  1 Dec 2017 10:26:40 -0800	[thread overview]
Message-ID: <20171201182640.21885-2-roy.franz@cavium.com> (raw)
In-Reply-To: <20171201182640.21885-1-roy.franz@cavium.com>

Fix trivial typo (an -> and) in description of service core masks.

Signed-off-by: Roy Franz <roy.franz@cavium.com>
---
 doc/guides/prog_guide/service_cores.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/prog_guide/service_cores.rst b/doc/guides/prog_guide/service_cores.rst
index 3a029ba9c..5a8d8941a 100644
--- a/doc/guides/prog_guide/service_cores.rst
+++ b/doc/guides/prog_guide/service_cores.rst
@@ -55,7 +55,7 @@ Service Core Initialization
 There are two methods to having service cores in a DPDK application, either by
 using the service coremask, or by dynamically adding cores using the API.
 The simpler of the two is to pass the `-s` coremask argument to EAL, which will
-take any cores available in the main DPDK coremask, an if the bits are also set
+take any cores available in the main DPDK coremask, and if the bits are also set
 in the service coremask the cores become service-cores instead of DPDK
 application lcores.
 
-- 
2.11.0

  reply	other threads:[~2017-12-01 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 18:26 [dpdk-dev] [PATCH 1/2] doc: Clarify wording regarding actions and flow rules Roy Franz
2017-12-01 18:26 ` Roy Franz [this message]
2017-12-11 15:20   ` [dpdk-dev] [PATCH 2/2] doc: Fix typo Mcnamara, John
2018-01-11 17:37     ` Thomas Monjalon
2017-12-04 13:51 ` [dpdk-dev] [PATCH 1/2] doc: Clarify wording regarding actions and flow rules Adrien Mazarguil

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=20171201182640.21885-2-roy.franz@cavium.com \
    --to=rfranz@cavium.com \
    --cc=dev@dpdk.org \
    --cc=roy.franz@cavium.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).