From: Jerin Jacob <jerinjacobk@gmail.com>
To: Muhammad Bilal <m.bilal@emumba.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] doc/guides/eventdevs: removing typing error in documentation of eventdevs
Date: Thu, 14 May 2020 21:02:29 +0530 [thread overview]
Message-ID: <CALBAE1MWvnnnKvhTdGxhETL4s8qNDEiWVagTrx1p4LM46cx_sQ@mail.gmail.com> (raw)
In-Reply-To: <20200514152651.11557-1-m.bilal@emumba.com>
On Thu, May 14, 2020 at 8:58 PM Muhammad Bilal <m.bilal@emumba.com> wrote:
>
> Bugzilla ID: 477
> Cc: dev@dpdk.org
> Cc: stable@dpdk.org
> Cc: jerinj@marvell.com
> Signed-off-by: Muhammad Bilal <m.bilal@emumba.com>
The same typo repeated for other places as well. Please send a single
patch for fixing all in one shot.
[master][dpdk.org] $ grep -ri "trough" *
doc/guides/eventdevs/index.rst:application trough the eventdev API.
drivers/net/mlx5/mlx5.c: * We have to perform
identification trough the ports.
lib/librte_vhost/rte_vhost.h: * about waiting packets. This is the
interrupt handling trough
> ---
> 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
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-05-14 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 15:26 [dpdk-stable] " Muhammad Bilal
2020-05-14 15:32 ` Jerin Jacob [this message]
2020-05-15 16:50 ` [dpdk-stable] [PATCH v2] removing typing error of word 'through' in multiple places Muhammad Bilal
2020-05-19 13:50 ` 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=CALBAE1MWvnnnKvhTdGxhETL4s8qNDEiWVagTrx1p4LM46cx_sQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=m.bilal@emumba.com \
--cc=stable@dpdk.org \
/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).