DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
	"Awal, Mohammad Abdul" <mohammad.abdul.awal@intel.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/ipsec: fix a typo in function name
Date: Wed, 19 Feb 2020 11:49:10 +0000	[thread overview]
Message-ID: <SN6PR11MB25582EE2BC68856B95735C649A100@SN6PR11MB2558.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200219112650.2260407-1-thomas@monjalon.net>

> 
> The name of the static function check_cryptodev_capablity()
> is fixed for the word "capability".
> There is no functional change.
> 
> The same typo is fixed in a comment in ip_fragmentation example.
> 
> Fixes: 05fe65eb66b2 ("test/ipsec: introduce functional test")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
>  app/test/test_ipsec.c            | 4 ++--
>  examples/ip_fragmentation/main.c | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/app/test/test_ipsec.c b/app/test/test_ipsec.c
> index 7dc83fee7e..9e14472938 100644
> --- a/app/test/test_ipsec.c
> +++ b/app/test/test_ipsec.c
> @@ -237,7 +237,7 @@ fill_crypto_xform(struct ipsec_unitest_params *ut_params,
>  }
> 
>  static int
> -check_cryptodev_capablity(const struct ipsec_unitest_params *ut,
> +check_cryptodev_capability(const struct ipsec_unitest_params *ut,
>  		uint8_t dev_id)
>  {
>  	struct rte_cryptodev_sym_capability_idx cap_idx;
> @@ -302,7 +302,7 @@ testsuite_setup(void)
> 
>  	/* Find first valid crypto device */
>  	for (i = 0; i < nb_devs; i++) {
> -		rc = check_cryptodev_capablity(ut_params, i);
> +		rc = check_cryptodev_capability(ut_params, i);
>  		if (rc == 0) {
>  			ts_params->valid_dev = i;
>  			ts_params->valid_dev_found = 1;
> diff --git a/examples/ip_fragmentation/main.c b/examples/ip_fragmentation/main.c
> index 104612339c..28febf49e7 100644
> --- a/examples/ip_fragmentation/main.c
> +++ b/examples/ip_fragmentation/main.c
> @@ -646,7 +646,7 @@ check_all_ports_link_status(uint32_t port_mask)
>  	}
>  }
> 
> -/* Check L3 packet type detection capablity of the NIC port */
> +/* Check L3 packet type detection capability of the NIC port */
>  static int
>  check_ptype(int portid)
>  {
> --

Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

> 2.25.0


  reply	other threads:[~2020-02-19 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 11:26 Thomas Monjalon
2020-02-19 11:49 ` Ananyev, Konstantin [this message]
2020-02-20 10:37   ` Akhil Goyal

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=SN6PR11MB25582EE2BC68856B95735C649A100@SN6PR11MB2558.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bernard.iremonger@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=mohammad.abdul.awal@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vladimir.medvedkin@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).