From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: x-fn-spp@sl.ntt-tx.co.jp
Cc: ferruh.yigit@intel.com, spp@dpdk.org
Subject: Re: [spp] [PATCH 0/6] add document for spp_pcap
Date: Fri, 25 Jan 2019 11:58:34 +0900 [thread overview]
Message-ID: <c4ed2980-fae2-6e8d-707a-310a9ad35b91@lab.ntt.co.jp> (raw)
In-Reply-To: <201901221142.x0MBgdB3022786@imss03.silk.ntt-tx.co.jp>
> From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
>
> This patch series is to add document for spp_pcap.
Series of patches applied. Thanks.
Acked-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
>
> Hideyuki Yamashita (6):
> docs: add command reference of spp_pcap
> docs: add spp_pcap into document of overview
> docs: add spp_pcap document of design
> docs: add spp_pcap into document of usecase
> docs: add spp_pcap into document of explanation
> docs: add spp_pcap into document of setup
>
> docs/guides/commands/secondary/index.rst | 1 +
> docs/guides/commands/secondary/spp_pcap.rst | 158 +++++++++++++++++
> docs/guides/spp_vf/design.rst | 98 ++++++++++-
> docs/guides/spp_vf/explain/functions_pcap.rst | 144 +++++++++++++++
> docs/guides/spp_vf/explain/index.rst | 1 +
> docs/guides/spp_vf/gsg/howto_use.rst | 39 ++++-
> docs/guides/spp_vf/gsg/setup.rst | 16 +-
> docs/guides/spp_vf/overview.rst | 34 +++-
> docs/guides/spp_vf/use_cases/index.rst | 3 +-
> docs/guides/spp_vf/use_cases/usecase3.rst | 164 ++++++++++++++++++
> 10 files changed, 645 insertions(+), 13 deletions(-)
> create mode 100644 docs/guides/commands/secondary/spp_pcap.rst
> create mode 100644 docs/guides/spp_vf/explain/functions_pcap.rst
> create mode 100644 docs/guides/spp_vf/use_cases/usecase3.rst
prev parent reply other threads:[~2019-01-25 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 11:42 x-fn-spp
2019-01-25 2:58 ` Yasufumi Ogawa [this message]
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=c4ed2980-fae2-6e8d-707a-310a9ad35b91@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
--cc=x-fn-spp@sl.ntt-tx.co.jp \
/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).