DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/19] fix hard-coded references in sample apps guide
Date: Mon, 07 Mar 2016 21:42:45 +0100	[thread overview]
Message-ID: <5111861.BHyDxOxj5n@xps13> (raw)
In-Reply-To: <1456419765-8566-1-git-send-email-mauricio.vasquezbernal@studenti.polito.it>

2016-02-25 18:02, Mauricio Vasquez B:
> MANY references in the sample applications user guide are wrong because
> they are hard-coded and section numbers have changed over the time.
> This patch set changes thoses references to dynamic ones, in this way if 
> section numbers change the reference get updated automatically.
> 
> Mauricio Vasquez B (19):
>   doc: fix vhost sample app hard-coded references
>   doc: fix distributor sample application hard-coded references
>   doc: fix exception path sample app hard-coded references
>   doc: fix intel quickAssist technology sample app hard-coded references
>   doc: fix ip fragmentation sample app hard-coded references
>   doc: fix ip reassembly sample app hard-coded references
>   doc: fix multicast sample app hard-coded references
>   doc: fix kepp alive sample app hard-coded references
>   doc: fix kni sample app hard-coded references
>   doc: fix l2 fwd sample app hard-coded references
>   doc: fix l3 fwd sample app hard-coded references
>   doc: fix l3fwd access control sample app hard-coded references
>   doc: fix l3fwd power man sample app hard-coded references
>   doc: fix l3fwd virtual sample app hard-coded references
>   doc: fix link status int sample app hard-coded references
>   doc: fix multi-process sample app hard-coded references
>   doc: fix tep termination sample app hard-coded references
>   doc: fix vmdq and dcb fwd sample app hard-coded references
>   doc: fix vm power man sample app hard-coded references

Applied as one patch with the above message, thanks

      parent reply	other threads:[~2016-03-07 20:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 17:02 Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 01/19] doc: fix vhost sample app hard-coded references Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 02/19] doc: fix distributor sample application " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 03/19] doc: fix exception path sample app " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 04/19] doc: fix intel quickAssist technology " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 05/19] doc: fix ip fragmentation " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 06/19] doc: fix ip reassembly " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 07/19] doc: fix multicast " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 08/19] doc: fix kepp alive " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 09/19] doc: fix kni " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 10/19] doc: fix l2 fwd " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 11/19] doc: fix l3 " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 12/19] doc: fix l3fwd access control " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 13/19] doc: fix l3fwd power man " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 14/19] doc: fix l3fwd virtual " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 15/19] doc: fix link status int " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 16/19] doc: fix multi-process " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 17/19] doc: fix tep termination " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 18/19] doc: fix vmdq and dcb fwd " Mauricio Vasquez B
2016-02-25 17:02 ` [dpdk-dev] [PATCH 19/19] doc: fix vm power man " Mauricio Vasquez B
2016-03-07 20:42 ` 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=5111861.BHyDxOxj5n@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=mauricio.vasquezbernal@studenti.polito.it \
    /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).