DPDK patches and discussions
 help / color / mirror / Atom feed
From: Muhammad Bilal <m.bilal@emumba.com>
To: jerinj@marvell.com, hemant.agrawal@nxp.com
Cc: dev@dpdk.org, Muhammad Bilal <m.bilal@emumba.com>, stable@dpdk.org
Subject: [dpdk-dev] [PATCH] doc/guides/eventdevs: removing typing error in documentation of eventdevs
Date: Thu, 14 May 2020 20:26:51 +0500	[thread overview]
Message-ID: <20200514152651.11557-1-m.bilal@emumba.com> (raw)

Bugzilla ID: 477
Cc: dev@dpdk.org
Cc: stable@dpdk.org
Cc: jerinj@marvell.com
Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
 doc/guides/eventdevs/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/eventdevs/index.rst b/doc/guides/eventdevs/index.rst
index 570905b81..bb66a5eac 100644
--- a/doc/guides/eventdevs/index.rst
+++ b/doc/guides/eventdevs/index.rst
@@ -5,7 +5,7 @@ Event Device Drivers
 The following are a list of event device PMDs, which can be used from an
-application trough the eventdev API.
+application through the eventdev API.
 .. toctree::
     :maxdepth: 2

             reply	other threads:[~2020-05-14 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 15:26 Muhammad Bilal [this message]
2020-05-14 15:32 ` Jerin Jacob
2020-05-15 16:50 ` [dpdk-dev] [PATCH v2] removing typing error of word 'through' in multiple places Muhammad Bilal
2020-05-19 13:50   ` [dpdk-dev] [dpdk-stable] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200514152651.11557-1-m.bilal@emumba.com \
    --to=m.bilal@emumba.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \


* 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).