From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 5/7] docs: remove spp_vm from secondary commands
Date: Thu, 17 Jan 2019 11:46:43 +0900 [thread overview]
Message-ID: <1547693205-17710-6-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1547693205-17710-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Remove spp_vm from Secondary Commands reference.
Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
docs/guides/commands/secondary/spp_vf.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/guides/commands/secondary/spp_vf.rst b/docs/guides/commands/secondary/spp_vf.rst
index cbb4859..3cf1cca 100644
--- a/docs/guides/commands/secondary/spp_vf.rst
+++ b/docs/guides/commands/secondary/spp_vf.rst
@@ -15,7 +15,7 @@ configuration, assigning or releasing resources.
Secondary ID is referred as ``--client-id`` which is given as an argument
while launching ``spp_vf``. It should be unique among all of secondary
-processes including ``spp_nfv``, ``spp_vm`` and others.
+processes including ``spp_nfv`` and others.
``vf`` command takes an secondary ID and one of sub commands. Secondary ID
and sub command should be separated with delimiter ``;``, or failed to a
--
2.7.4
next prev parent reply other threads:[~2019-01-17 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 2:46 [spp] [PATCH 0/7] Remove spp_vm from documentation ogawa.yasufumi
2019-01-17 2:46 ` [spp] [PATCH 1/7] docs: remove spp_vm from howto use section ogawa.yasufumi
2019-01-17 2:46 ` [spp] [PATCH 2/7] docs: remove spp_vm from spp-ctl API ogawa.yasufumi
2019-01-17 2:46 ` [spp] [PATCH 3/7] docs: remove spp_vm from SPP container ogawa.yasufumi
2019-01-17 2:46 ` [spp] [PATCH 4/7] docs: remove spp_vm from usecases ogawa.yasufumi
2019-01-17 2:46 ` ogawa.yasufumi [this message]
2019-01-17 2:46 ` [spp] [PATCH 6/7] docs: remove spp_vf from image of usecase ogawa.yasufumi
2019-01-17 2:46 ` [spp] [PATCH 7/7] docs: update hugepages setup ogawa.yasufumi
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=1547693205-17710-6-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@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).