From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: spp@dpdk.org
Subject: [spp] Move SPP VF documentation
Date: Tue, 5 Feb 2019 19:23:32 +0900 [thread overview]
Message-ID: <8d2d67f9-dcb8-0d12-1b25-bdcf83847f8e@lab.ntt.co.jp> (raw)
Hi all,
In SPP documentation, spp_vf and its siblings are described in chapter `SPP VF` dependently, but should be under each of other
chapters as similar to spp_nfv. Spp_vf was almost completely separated from SPP and controlled from dedicated CLI, `spp_vf.py`.
However, it is unified to SPP now. Documentation should be also unified to. I would like to start to move these documents after
spp_pcap Hideyuki has proposed is merged.
Thanks,
Yasufumi
reply other threads:[~2019-02-05 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8d2d67f9-dcb8-0d12-1b25-bdcf83847f8e@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--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).