From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 2/4] doc: update the dpaa2 eventdev extra paths
Date: Mon, 24 Jul 2017 12:53:47 +0530 [thread overview]
Message-ID: <1500881029-1005-2-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1500881029-1005-1-git-send-email-hemant.agrawal@nxp.com>
The DPDK helper for NXP devices is not dpdk-extras
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
doc/guides/eventdevs/dpaa2.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/eventdevs/dpaa2.rst b/doc/guides/eventdevs/dpaa2.rst
index 3382d59..0970b26 100644
--- a/doc/guides/eventdevs/dpaa2.rst
+++ b/doc/guides/eventdevs/dpaa2.rst
@@ -94,12 +94,12 @@ separately:
SDK and related information can be obtained from: `NXP QorIQ SDK <http://www.nxp.com/products/software-and-tools/run-time-software/linux-sdk/linux-sdk-for-qoriq-processors:SDKLINUX>`_.
-- **DPDK Helper Scripts**
+- **DPDK Extra Scripts**
DPAA2 based resources can be configured easily with the help of ready scripts
- as provided in the DPDK helper repository.
+ as provided in the DPDK Extra repository.
- `DPDK Helper Scripts <https://github.com/qoriq-open-source/dpdk-helper>`_.
+ `DPDK Extras Scripts <https://github.com/qoriq-open-source/dpdk-extras>`_.
Currently supported by DPDK:
--
2.7.4
next prev parent reply other threads:[~2017-07-24 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 7:23 [dpdk-dev] [PATCH 1/4] doc: update release notes for DPAA2 eventdev Hemant Agrawal
2017-07-24 7:23 ` Hemant Agrawal [this message]
2017-07-24 7:23 ` [dpdk-dev] [PATCH 3/4] doc: update release notes for dpaa2 changes Hemant Agrawal
2017-07-24 7:23 ` [dpdk-dev] [PATCH 4/4] doc: update dpaa2 PMD document Hemant Agrawal
2017-07-30 21:23 ` [dpdk-dev] [PATCH 1/4] doc: update release notes for DPAA2 eventdev 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=1500881029-1005-2-git-send-email-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.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).