From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Update programmers guide doc, mbuf chapter
Date: Tue, 2 Dec 2014 16:17:57 +0000 [thread overview]
Message-ID: <1417537079-476-1-git-send-email-bruce.richardson@intel.com> (raw)
These patches contain updates to the programmers guide document to keep it in
sync with the code changes made to the rte_mbuf data structure.
Bruce Richardson (2):
doc: update mbuf section of programmer's guide for 1.8
doc: Updated image files for rte_mbuf changes in 1.8
doc/guides/prog_guide/img/mbuf1.svg | 44 +++++++++++++---------------
doc/guides/prog_guide/img/mbuf2.svg | 57 ++++++++++++++++++-------------------
doc/guides/prog_guide/mbuf_lib.rst | 22 +++++++-------
3 files changed, 59 insertions(+), 64 deletions(-)
--
2.1.1
next reply other threads:[~2014-12-02 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 16:17 Bruce Richardson [this message]
2014-12-02 16:17 ` [dpdk-dev] [PATCH 1/2] doc: update mbuf section of programmer's guide for 1.8 Bruce Richardson
2014-12-18 20:30 ` Iremonger, Bernard
2014-12-02 16:17 ` [dpdk-dev] [PATCH 2/2] doc: Updated image files for rte_mbuf changes in 1.8 Bruce Richardson
2014-12-12 11:21 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2014-12-18 21:02 ` Iremonger, Bernard
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=1417537079-476-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@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).