DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	<zbigniew.bodek@caviumnetworks.com>,
	<jerin.jacob@caviumnetworks.com>, <hemant.agrawal@nxp.com>,
	<fiona.trahe@intel.com>, <deepak.k.jain@intel.com>,
	 <john.griffin@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: fix session init return value
Date: Tue, 25 Jul 2017 14:03:27 +0530	[thread overview]
Message-ID: <6905df02-6f11-a53e-f5cb-24498007a530@nxp.com> (raw)
In-Reply-To: <20170724085428.51995-1-pablo.de.lara.guarch@intel.com>

On 7/24/2017 2:24 PM, Pablo de Lara wrote:
> When calling rte_cryptodev_sym_session_init(),
> if there was an error, it returned -1, regardless
> the error.
> Instead, it should return the specific error code, which can
> be valuable for the application for error handling.
> 
> Fixes: b3bbd9e5f265 ("cryptodev: support device independent sessions")
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>   drivers/crypto/aesni_gcm/aesni_gcm_pmd.c       |   8 +-
>   drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c   |  12 +-
>   drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c     |  30 +++--
>   drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c |  12 +-
>   drivers/crypto/armv8/rte_armv8_pmd.c           |  14 +--
>   drivers/crypto/armv8/rte_armv8_pmd_ops.c       |  10 +-
>   drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c    |  10 +-
>   drivers/crypto/kasumi/rte_kasumi_pmd.c         |   6 +-
>   drivers/crypto/kasumi/rte_kasumi_pmd_ops.c     |  10 +-
>   drivers/crypto/null/null_crypto_pmd.c          |   4 +-
>   drivers/crypto/null/null_crypto_pmd_ops.c      |  10 +-
>   drivers/crypto/openssl/rte_openssl_pmd.c       |  24 ++--
>   drivers/crypto/openssl/rte_openssl_pmd_ops.c   |  11 +-
>   drivers/crypto/qat/qat_crypto.c                | 162 +++++++++++++++----------
>   drivers/crypto/scheduler/scheduler_pmd_ops.c   |   8 +-
>   drivers/crypto/snow3g/rte_snow3g_pmd.c         |   6 +-
>   drivers/crypto/snow3g/rte_snow3g_pmd_ops.c     |  10 +-
>   drivers/crypto/zuc/rte_zuc_pmd.c               |   6 +-
>   drivers/crypto/zuc/rte_zuc_pmd_ops.c           |  10 +-
>   lib/librte_cryptodev/rte_cryptodev.c           |   8 +-
>   lib/librte_cryptodev/rte_cryptodev.h           |   4 +-
>   lib/librte_cryptodev/rte_cryptodev_pmd.h       |   4 +-
>   test/test/test_cryptodev.c                     |   4 +-
>   23 files changed, 222 insertions(+), 161 deletions(-)
> 

Acked for dpaa2_sec, librte_cryptodev, test

  parent reply	other threads:[~2017-07-25  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  8:54 Pablo de Lara
2017-07-25  6:16 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2017-07-27 10:12   ` Trahe, Fiona
2017-07-27 15:26     ` De Lara Guarch, Pablo
2017-07-25  8:33 ` Akhil Goyal [this message]
2017-07-25 11:55 ` [dpdk-dev] [PATCH] " Trahe, Fiona

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=6905df02-6f11-a53e-f5cb-24498007a530@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.griffin@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=zbigniew.bodek@caviumnetworks.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).