From: Baruch Siach <baruch@tkos.co.il>
To: dev@dpdk.org
Cc: John McNamara <john.mcnamara@intel.com>,
Baruch Siach <baruch@tkos.co.il>
Subject: [dpdk-dev] [PATCH v2 2/3] doc: correct the description of the app directory
Date: Tue, 6 Dec 2016 14:38:09 +0200 [thread overview]
Message-ID: <8fc9b97c4944544bc680351fb7e72a821275ca4d.1481027890.git.baruch@tkos.co.il> (raw)
In-Reply-To: <04aef536b67faf3c09e0f4603736057f95b5ef66.1481027890.git.baruch@tkos.co.il>
The applications under the app directory are just that, not sample
applications.
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
v2: New patch (John M)
---
doc/guides/prog_guide/source_org.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/prog_guide/source_org.rst b/doc/guides/prog_guide/source_org.rst
index be4b564fb23e..27e18e8951a0 100644
--- a/doc/guides/prog_guide/source_org.rst
+++ b/doc/guides/prog_guide/source_org.rst
@@ -125,7 +125,7 @@ Applications
Applications are source files that contain a ``main()`` function.
They are located in the ``$(RTE_SDK)/app`` and ``$(RTE_SDK)/examples`` directories.
-The app directory contains sample applications that are used to test DPDK (such as autotests)
+The app directory contains applications that are used to test DPDK (such as autotests)
or the Poll Mode Drivers (test-pmd)::
app
--
2.10.2
next prev parent reply other threads:[~2016-12-06 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 12:38 [dpdk-dev] [PATCH v2 1/3] doc: note that the app list is incomplete Baruch Siach
2016-12-06 12:38 ` Baruch Siach [this message]
2016-12-06 12:48 ` [dpdk-dev] [PATCH v2 2/3] doc: correct the description of the app directory Mcnamara, John
2016-12-06 12:38 ` [dpdk-dev] [PATCH v2 3/3] doc: consistently quote directory names Baruch Siach
2016-12-06 12:48 ` Mcnamara, John
2016-12-06 12:48 ` [dpdk-dev] [PATCH v2 1/3] doc: note that the app list is incomplete Mcnamara, John
2016-12-06 16:53 ` Thomas Monjalon
2017-02-09 14:49 ` 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=8fc9b97c4944544bc680351fb7e72a821275ca4d.1481027890.git.baruch@tkos.co.il \
--to=baruch@tkos.co.il \
--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).