DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	Declan Doherty <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix typo
Date: Fri, 26 Jul 2019 14:03:23 +0000	[thread overview]
Message-ID: <VE1PR04MB6639C16ED8DA80332752FB56E6C00@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190726134223.94782-1-ferruh.yigit@intel.com>


> 
> Remove extra ';' which is probably added unintentionally, reported by
> ./devtools/check-includes.sh script.
> 
> Fixes: 26008aaed14c ("cryptodev: add asymmetric xform and op definitions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
>  lib/librte_cryptodev/rte_crypto_asym.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/librte_cryptodev/rte_crypto_asym.h
> b/lib/librte_cryptodev/rte_crypto_asym.h
> index 044224214..4fbef2f89 100644
> --- a/lib/librte_cryptodev/rte_crypto_asym.h
> +++ b/lib/librte_cryptodev/rte_crypto_asym.h
> @@ -383,7 +383,7 @@ struct rte_cryptodev_asym_session;
>   */
>  struct rte_crypto_rsa_op_param {
>  	enum rte_crypto_asym_op_type op_type;
> -	/**< Type of RSA operation for transform */;
> +	/**< Type of RSA operation for transform */
> 
>  	rte_crypto_param message;
>  	/**<
> --
> 2.21.0

Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2019-07-26 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26 13:42 Ferruh Yigit
2019-07-26 14:03 ` Akhil Goyal [this message]

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=VE1PR04MB6639C16ED8DA80332752FB56E6C00@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=pablo.de.lara.guarch@intel.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).