From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, john.mcnamara@intel.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] flow classify documentation
Date: Thu, 26 Oct 2017 10:09:15 +0100 [thread overview]
Message-ID: <1509008957-11812-1-git-send-email-bernard.iremonger@intel.com> (raw)
This patch set contains documention files for the
Flow Classify library and the Flow Classify sample
application.
Both patches update the MAINTAINERS file.
Bernard Iremonger (2):
doc: flow classify library prog guide
doc: flow classify sample app guide
MAINTAINERS | 2 +
doc/guides/prog_guide/flow_classify_lib.rst | 427 ++++++++++++++++++++
doc/guides/prog_guide/index.rst | 1 +
doc/guides/sample_app_ug/flow_classify.rst | 592 ++++++++++++++++++++++++++++
doc/guides/sample_app_ug/index.rst | 1 +
5 files changed, 1023 insertions(+)
create mode 100644 doc/guides/prog_guide/flow_classify_lib.rst
create mode 100644 doc/guides/sample_app_ug/flow_classify.rst
--
1.9.1
next reply other threads:[~2017-10-26 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 9:09 Bernard Iremonger [this message]
2017-10-26 9:09 ` [dpdk-dev] [PATCH 1/2] doc: flow classify library prog guide Bernard Iremonger
2017-11-02 16:58 ` Mcnamara, John
2017-11-02 17:29 ` Iremonger, Bernard
2017-11-03 9:52 ` Mcnamara, John
2017-11-03 15:32 ` Iremonger, Bernard
2017-10-26 9:09 ` [dpdk-dev] [PATCH 2/2] doc: flow classify sample app guide Bernard Iremonger
2017-11-02 17:00 ` Mcnamara, John
2017-11-02 17:32 ` Iremonger, Bernard
2017-11-03 11:13 ` [dpdk-dev] [PATCH v2] flow classify documentation Bernard Iremonger
2017-11-03 11:13 ` [dpdk-dev] [PATCH v2] doc: flow classify guides Bernard Iremonger
2017-11-03 15:34 ` Mcnamara, John
2017-11-07 22:00 ` Thomas Monjalon
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=1509008957-11812-1-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).