patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Sarosh Arif <sarosh.arif@emumba.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc: fix typing error
Date: Thu, 18 Jun 2020 02:06:00 +0000	[thread overview]
Message-ID: <BY5PR11MB445184B3B5E205E2FB087165F89B0@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200616082201.23035-1-sarosh.arif@emumba.com>

From: Sarosh Arif :
> fixed typing error in doc/guides/tools/testbbdev.rst
> 
> Fixes: f714a18885a6 ("app/testbbdev: add test application for bbdev")
> Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
> ---
>  doc/guides/tools/testbbdev.rst | 2 +-

Thanks.
Acked-by: Nic Chautru <nicolas.chautru@intel.com>

>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/doc/guides/tools/testbbdev.rst b/doc/guides/tools/testbbdev.rst
> index 279872139..393c3e9d0 100644
> --- a/doc/guides/tools/testbbdev.rst
> +++ b/doc/guides/tools/testbbdev.rst
> @@ -6,7 +6,7 @@ dpdk-test-bbdev Application
> 
>  The ``dpdk-test-bbdev`` tool is a Data Plane Development Kit (DPDK) utility
> that  allows measuring performance parameters of PMDs available in the
> bbdev framework.
> -Available tests available for execution are: latency, throughput, validation,
> +Tests available for execution are: latency, throughput, validation,
>  bler and sanity tests. Execution of tests can be customized using various
> parameters passed to a python running script.
> 
> --
> 2.17.1


  reply	other threads:[~2020-06-18  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  8:22 Sarosh Arif
2020-06-18  2:06 ` Chautru, Nicolas [this message]
2020-07-22  0:09   ` [dpdk-stable] [dpdk-dev] " 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=BY5PR11MB445184B3B5E205E2FB087165F89B0@BY5PR11MB4451.namprd11.prod.outlook.com \
    --to=nicolas.chautru@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=sarosh.arif@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).