Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 3/6] docs: move images of spp_pcap
Date: Fri, 15 Feb 2019 02:26:57 +0900	[thread overview]
Message-ID: <20190214172700.5816-4-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <20190214172700.5816-1-ogawa.yasufumi@lab.ntt.co.jp>

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

Correct path of images of spp_pcap placed in `images/spp_pcap` but
should be in `images/spp_vf` conventionally.

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_design.svg   | 0
 docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_overview.svg | 0
 docs/guides/spp_vf/design.rst                                 | 2 +-
 docs/guides/spp_vf/overview.rst                               | 4 ++--
 docs/guides/spp_vf/use_cases/usecase3.rst                     | 4 ++--
 5 files changed, 5 insertions(+), 5 deletions(-)
 rename docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_design.svg (100%)
 rename docs/guides/images/{spp_pcap => spp_vf}/spp_pcap_overview.svg (100%)

diff --git a/docs/guides/images/spp_pcap/spp_pcap_design.svg b/docs/guides/images/spp_vf/spp_pcap_design.svg
similarity index 100%
rename from docs/guides/images/spp_pcap/spp_pcap_design.svg
rename to docs/guides/images/spp_vf/spp_pcap_design.svg
diff --git a/docs/guides/images/spp_pcap/spp_pcap_overview.svg b/docs/guides/images/spp_vf/spp_pcap_overview.svg
similarity index 100%
rename from docs/guides/images/spp_pcap/spp_pcap_overview.svg
rename to docs/guides/images/spp_vf/spp_pcap_overview.svg
diff --git a/docs/guides/spp_vf/design.rst b/docs/guides/spp_vf/design.rst
index 89b7059..b1e864a 100644
--- a/docs/guides/spp_vf/design.rst
+++ b/docs/guides/spp_vf/design.rst
@@ -131,7 +131,7 @@ packets from ``phy:0`` are captured by using three ``writer`` threads.
 
 .. _figure_spp_pcap_design:
 
-.. figure:: ../images/spp_pcap/spp_pcap_design.*
+.. figure:: ../images/spp_vf/spp_pcap_design.*
     :width: 55%
 
     spp_pcap internal structure
diff --git a/docs/guides/spp_vf/overview.rst b/docs/guides/spp_vf/overview.rst
index 09c21af..adaced6 100644
--- a/docs/guides/spp_vf/overview.rst
+++ b/docs/guides/spp_vf/overview.rst
@@ -101,7 +101,7 @@ threads unlike spp_vf.
 
 .. _figure_spp_pcap_overview:
 
-.. figure:: ../images/spp_pcap/spp_pcap_overview.*
-   :width: 55%
+.. figure:: ../images/spp_vf/spp_pcap_overview.*
+   :width: 50%
 
    Overview of spp_pcap
diff --git a/docs/guides/spp_vf/use_cases/usecase3.rst b/docs/guides/spp_vf/use_cases/usecase3.rst
index 146ef06..c31324e 100644
--- a/docs/guides/spp_vf/use_cases/usecase3.rst
+++ b/docs/guides/spp_vf/use_cases/usecase3.rst
@@ -13,8 +13,8 @@ Incoming packets received by ``phy:0`` is captured by ``spp_pcap``.
 
 .. _figure_simple_capture:
 
-.. figure:: ../../images/spp_pcap/spp_pcap_overview.*
-    :width: 40%
+.. figure:: ../../images/spp_vf/spp_pcap_overview.*
+    :width: 50%
 
     Simple Packet Capture
 
-- 
2.17.1

  parent 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 [spp] [PATCH 0/6] Update docs " ogawa.yasufumi
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 ` ogawa.yasufumi [this message]
2019-02-14 17:26 ` [spp] [PATCH 4/6] docs: update overview image of spp_pcap 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-4-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).