From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/6] Update docs of spp_pcap
Date: Fri, 15 Feb 2019 02:26:54 +0900 [thread overview]
Message-ID: <20190214172700.5816-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
This series of patches is to update docs of spp_pcap for typos, old
descriptions and lackness of explanations.
Yasufumi Ogawa (6):
docs: update design and howto use of spp_pcap
docs: update spp_pcap commands
docs: move images of spp_pcap
docs: update overview image of spp_pcap
docs: rename files of usecases in spp_vf
docs: update usecase of spp_pcap
docs/guides/commands/secondary/spp_pcap.rst | 109 +++++---
.../{spp_pcap => spp_vf}/spp_pcap_design.svg | 71 ++----
.../spp_pcap_overview.svg | 0
docs/guides/spp_vf/design.rst | 95 ++-----
docs/guides/spp_vf/gsg/howto_use.rst | 101 +++++---
docs/guides/spp_vf/overview.rst | 4 +-
docs/guides/spp_vf/use_cases/index.rst | 10 +-
...c_usecase_mirror.rst => mirror_simple.rst} | 0
.../{usecase2.rst => mirror_vms.rst} | 0
docs/guides/spp_vf/use_cases/pcap_simple.rst | 235 ++++++++++++++++++
docs/guides/spp_vf/use_cases/usecase3.rst | 164 ------------
.../{basic_usecase_vf.rst => vf_simple.rst} | 0
.../{usecase1.rst => vf_ssh_login.rst} | 0
13 files changed, 409 insertions(+), 380 deletions(-)
rename docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_design.svg (90%)
rename docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_overview.svg (100%)
rename docs/guides/spp_vf/use_cases/{basic_usecase_mirror.rst => mirror_simple.rst} (100%)
rename docs/guides/spp_vf/use_cases/{usecase2.rst => mirror_vms.rst} (100%)
create mode 100644 docs/guides/spp_vf/use_cases/pcap_simple.rst
delete mode 100644 docs/guides/spp_vf/use_cases/usecase3.rst
rename docs/guides/spp_vf/use_cases/{basic_usecase_vf.rst => vf_simple.rst} (100%)
rename docs/guides/spp_vf/use_cases/{usecase1.rst => vf_ssh_login.rst} (100%)
--
2.17.1
next reply other threads:[~2019-02-14 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 17:26 ogawa.yasufumi [this message]
2019-02-14 17:26 ` [spp] [PATCH 1/6] docs: update design and howto use " ogawa.yasufumi
2019-02-14 17:26 ` [spp] [PATCH 2/6] docs: update spp_pcap commands ogawa.yasufumi
2019-02-14 17:26 ` [spp] [PATCH 3/6] docs: move images of spp_pcap ogawa.yasufumi
2019-02-14 17:26 ` [spp] [PATCH 4/6] docs: update overview image " ogawa.yasufumi
2019-02-14 17:26 ` [spp] [PATCH 5/6] docs: rename files of usecases in spp_vf ogawa.yasufumi
2019-02-14 17:27 ` [spp] [PATCH 6/6] docs: update usecase of spp_pcap 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=20190214172700.5816-1-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).