DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <rami.rosen@intel.com>
To: dev@dpdk.org
Cc: jingjing.wu@intel.com, Rami Rosen <rami.rosen@intel.com>
Subject: [dpdk-dev] [PATCH ] doc: Fix a typo in a section about i40e PMD limitation.
Date: Mon,  3 Apr 2017 00:12:11 -0400	[thread overview]
Message-ID: <20170403041211.15373-1-rami.rosen@intel.com> (raw)

This patch fixes a trivial typo in i40e documentation;
commit edf1b ("add limitations for i40e PMD") added a comment about 
the behaviour upon DPDK application quit; however, it was wrongly titled
as "after DPDK application exist" instead of "after DPDK application exit",
and this trivial patch fixes it. 

Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
 doc/guides/nics/i40e.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 043de34..413661c 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -445,7 +445,7 @@ is used as the VF driver, DPDK cannot choose 16 byte receive descriptor. That
 is to say, user should keep ``CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n`` in
 config file.
 
-Link down with i40e kernel driver after DPDK application exist
+Link down with i40e kernel driver after DPDK application exit
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 After DPDK application quit, and the device is bound back to Linux i40e
-- 
2.9.3

             reply	other threads:[~2017-04-02 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  4:12 Rami Rosen [this message]
2017-04-03  7:08 ` Mcnamara, John
2017-04-03 12:28   ` Ferruh Yigit

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=20170403041211.15373-1-rami.rosen@intel.com \
    --to=rami.rosen@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).