From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto: fix control issues in aesni pmd
Date: Tue, 31 May 2016 11:39:34 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9560AF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1464018398-71742-1-git-send-email-deepak.k.jain@intel.com>
Hi Deepak,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Deepak Kumar Jain
> Sent: Monday, May 23, 2016 4:47 PM
> To: Doherty, Declan
> Cc: Jain, Deepak K; dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] crypto: fix control issues in aesni pmd
>
Since this patch is for the AES-NI Multi Buffer PMD, you should change the title to
"aesni_mb: fix...", and of couse without to including then aesni pmd again :)
> From: "Jain, Deepak K" <deepak.k.jain@intel.com>
>
> Fix the control issues for return value
Maybe a more descriptive commit would be something like "Fix wrong indentation for return value",
probably applicable for the title too.
>
> Fixes: 924e84f87306 ("aesni_mb: add driver for multi buffer based crypto")
> Coverity ID 126585
Also, take a look at this email and change the commit accordingly, as it fixes a Coverity issue:
http://dpdk.org/ml/archives/dev/2016-May/039650.html
Thanks,
Pablo
>
> Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
> ---
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
> b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
> index 3415ac1..9c42f88 100644
> --- a/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
> +++ b/drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c
> @@ -560,7 +560,7 @@ aesni_mb_pmd_enqueue_burst(void *queue_pair,
> struct rte_crypto_op **ops,
> goto flush_jobs;
> else
> qp->stats.enqueued_count += processed_jobs;
> - return i;
> + return i;
>
> flush_jobs:
> /*
> --
> 2.5.5
prev parent reply other threads:[~2016-05-31 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 15:46 Deepak Kumar Jain
2016-05-31 11:39 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8973C9560AF@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@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).