From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John Guzik <john@shieldxnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: Programmers guide IP fragmentation direct/indirect mbufs to wrong section
Date: Mon, 11 Apr 2016 20:57:08 +0200 [thread overview]
Message-ID: <2740899.KCQQlYyY3K@xps13> (raw)
In-Reply-To: <1460399087-23904-1-git-send-email-john@shieldxnetworks.com>
2016-04-11 11:24, John Guzik:
> --- a/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
> +++ b/doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
> -For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 7.7 Direct and Indirect Buffers.*
> +For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 6.7 Direct and Indirect Buffers.*
We should replace it by a link.
There are some remaining hard references in the docs:
doc/guides/nics/virtio.rst:
For more details about kni, please refer to Chapter 24 "Kernel NIC Interface".
doc/guides/prog_guide/ip_fragment_reassembly_lib.rst:
For more information about direct and indirect mbufs, refer to the *DPDK Programmers guide 7.7 Direct and Indirect Buffers.*
doc/guides/sample_app_ug/multi_process.rst:
(refer to *DPDK Programmer's Guide* , Section 6.4, "Local Cache")
prev parent reply other threads:[~2016-04-11 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 18:24 John Guzik
2016-04-11 18:57 ` Thomas Monjalon [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=2740899.KCQQlYyY3K@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john@shieldxnetworks.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).