DPDK patches and discussions
 help / color / mirror / Atom feed
From: Julien Castets <castets.j@gmail.com>
To: dev@dpdk.org
Cc: Julien Castets <jcastets@scaleway.com>
Subject: [dpdk-dev] [PATCH] doc: fix renamed bind tool
Date: Mon,  6 Mar 2017 17:15:26 +0100	[thread overview]
Message-ID: <20170306161526.42298-1-castets.j@gmail.com> (raw)
In-Reply-To: <1715418.2m34KmC0GB@xps13>

From: Julien Castets <jcastets@scaleway.com>

Signed-off-by: Julien Castets <jcastets@scaleway.com>
---
 doc/guides/linux_gsg/build_dpdk.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/linux_gsg/build_dpdk.rst b/doc/guides/linux_gsg/build_dpdk.rst
index eadade276..9d245737d 100644
--- a/doc/guides/linux_gsg/build_dpdk.rst
+++ b/doc/guides/linux_gsg/build_dpdk.rst
@@ -208,7 +208,7 @@ Any network ports under Linux* control will be ignored by the DPDK poll-mode dri
 
 To bind ports to the ``uio_pci_generic``, ``igb_uio`` or ``vfio-pci`` module for DPDK use,
 and then subsequently return ports to Linux* control,
-a utility script called dpdk_nic _bind.py is provided in the usertools subdirectory.
+a utility script called dpdk-devbind.py is provided in the usertools subdirectory.
 This utility can be used to provide a view of the current state of the network ports on the system,
 and to bind and unbind those ports from the different kernel modules, including the uio and vfio modules.
 The following are some examples of how the script can be used.
-- 
2.11.0

  reply	other threads:[~2017-03-06 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 13:58 [dpdk-dev] [PATCH] Fix doc: dpdk_nic_bind.py renamed to dpdk-devbind.py Julien Castets
2017-03-06 15:31 ` Thomas Monjalon
2017-03-06 16:15   ` Julien Castets [this message]
2017-03-06 16:28     ` [dpdk-dev] [PATCH] doc: fix renamed bind tool 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=20170306161526.42298-1-castets.j@gmail.com \
    --to=castets.j@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jcastets@scaleway.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).