patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Muhammad Bilal <m.bilal@emumba.com>
To: jerinj@marvell.com, shahafs@mellanox.com, xiaolong.ye@intel.com
Cc: dev@dpdk.org, Muhammad Bilal <m.bilal@emumba.com>,
	stable@dpdk.org, matan@mellanox.com, maxime.coquelin@redhat.com
Subject: [dpdk-stable] [PATCH v2] removing typing error of word 'through' in multiple places
Date: Fri, 15 May 2020 21:50:54 +0500	[thread overview]
Message-ID: <20200515165054.26973-1-m.bilal@emumba.com> (raw)
In-Reply-To: <20200514152651.11557-1-m.bilal@emumba.com>

Removed the typing error in doc/guides/eventdevs/index.rst,
drivers/net/mlx5/mlx5.c and in lib/librte_vhost/rte_vhost.h

Cc: dev@dpdk.org
Cc: stable@dpdk.org
Cc: jerinj@marvell.com
Cc: matan@mellanox.com
Cc: shahafs@mellanox.com
Cc: maxime.coquelin@redhat.com
Cc: xiaolong.ye@intel.com
Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
---
 doc/guides/eventdevs/index.rst | 2 +-
 drivers/net/mlx5/mlx5.c        | 2 +-
 lib/librte_vhost/rte_vhost.h   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

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
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 4f704cbef..264f4928a 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -3382,7 +3382,7 @@ mlx5_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
 		/*
 		 * Single IB device with multiple ports found,
 		 * it may be E-Switch master device and representors.
-		 * We have to perform identification trough the ports.
+		 * We have to perform identification through the ports.
 		 */
 		MLX5_ASSERT(nl_rdma >= 0);
 		MLX5_ASSERT(ns == 0);
diff --git a/lib/librte_vhost/rte_vhost.h b/lib/librte_vhost/rte_vhost.h
index 5c72fba79..d43669f2c 100644
--- a/lib/librte_vhost/rte_vhost.h
+++ b/lib/librte_vhost/rte_vhost.h
@@ -259,7 +259,7 @@ struct vhost_device_ops {
 
 	/**
 	 * This callback gets called each time a guest gets notified
-	 * about waiting packets. This is the interrupt handling trough
+	 * about waiting packets. This is the interrupt handling through
 	 * the eventfd_write(callfd), which can be used for counting these
 	 * "slow" syscalls.
 	 */
-- 
2.17.1


  parent reply	other threads:[~2020-05-15 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 15:26 [dpdk-stable] [PATCH] doc/guides/eventdevs: removing typing error in documentation of eventdevs Muhammad Bilal
2020-05-14 15:32 ` [dpdk-stable] [dpdk-dev] " Jerin Jacob
2020-05-15 16:50 ` Muhammad Bilal [this message]
2020-05-19 13:50   ` [dpdk-stable] [PATCH v2] removing typing error of word 'through' in multiple places 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=20200515165054.26973-1-m.bilal@emumba.com \
    --to=m.bilal@emumba.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=matan@mellanox.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=xiaolong.ye@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).