patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Cc: akhil.goyal@nxp.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] examples/vhost_crypto: fix bracket
Date: Tue, 11 Dec 2018 19:14:30 +0100	[thread overview]
Message-ID: <9fcc4310-e188-668c-74c9-4ea3c995f19b@redhat.com> (raw)
In-Reply-To: <20181211150951.22665-1-roy.fan.zhang@intel.com>



On 12/11/18 4:09 PM, Fan Zhang wrote:
> This patch fixes a missed bracket bug in the code.
> 
> Fixes: e1d90eaa83ff ("examples/vhost_crypto: fix zero copy")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>   examples/vhost_crypto/main.c | 9 +++++----
>   1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/examples/vhost_crypto/main.c b/examples/vhost_crypto/main.c
> index f08babd97..3deb5263f 100644
> --- a/examples/vhost_crypto/main.c
> +++ b/examples/vhost_crypto/main.c
> @@ -503,11 +503,12 @@ main(int argc, char *argv[])
>   			if (strstr(dev_info.driver_name,
>   				RTE_STR(VHOST_CRYPTO_CDEV_NAME_AESNI_MB_PMD)) ||
>   				strstr(dev_info.driver_name,
> -				RTE_STR(VHOST_CRYPTO_CDEV_NAME_AESNI_GCM_PMD)))
> -			RTE_LOG(ERR, USER1, "Cannot enable zero-copy in %s\n",
> +				RTE_STR(VHOST_CRYPTO_CDEV_NAME_AESNI_GCM_PMD))) {
> +				RTE_LOG(ERR, USER1, "Cannot enable zero-copy in %s\n",
>   					dev_info.driver_name);
> -			ret = -EPERM;
> -			goto error_exit;
> +				ret = -EPERM;
> +				goto error_exit;
> +			}
>   		}
>   
>   		if (dev_info.max_nb_queue_pairs < info->qid + 1) {
> 


Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime

  reply	other threads:[~2018-12-11 18:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 15:09 [dpdk-stable] " Fan Zhang
2018-12-11 18:14 ` Maxime Coquelin [this message]
2018-12-11 18:34 ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin

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=9fcc4310-e188-668c-74c9-4ea3c995f19b@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=roy.fan.zhang@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).