From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Somarowthu, Naga SureshX" <naga.sureshx.somarowthu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/kasumi: add dynamic logging to kasumi
Date: Wed, 27 Jun 2018 15:38:06 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8DDC74@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1529904182-8878-1-git-send-email-naga.sureshx.somarowthu@intel.com>
Hi Naga,
Two last comments below.
> -----Original Message-----
> From: Somarowthu, Naga SureshX
> Sent: Monday, June 25, 2018 6:23 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Pattan, Reshma
> <reshma.pattan@intel.com>; Somarowthu, Naga SureshX
> <naga.sureshx.somarowthu@intel.com>
> Subject: [PATCH] crypto/kasumi: add dynamic logging to kasumi
>
> 1.added new logtype for kasumi driver.
> 2.registered new logtype.
> 3.KASUMI_LOG_ERR and CDEV_LOG_ERR are
> replaced with new logtype name KASUMI_PMD_LOG.
>
> Signed-off-by: Naga Suresh Somarowthu
> <naga.sureshx.somarowthu@intel.com>
> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
...
> if (cipher_xform) {
> /* Only KASUMI F8 supported */
> if (cipher_xform->cipher.algo !=
> RTE_CRYPTO_CIPHER_KASUMI_F8)
> + KASUMI_PMD_LOG(ERR, "Unsupported cipher
> algorithm ");
> return -ENOTSUP;
Missing braces, as there are two lines inside the if statement.
>
> sess->cipher_iv_offset = cipher_xform->cipher.iv.offset;
> if (cipher_xform->cipher.iv.length != KASUMI_IV_LENGTH) {
> - KASUMI_LOG_ERR("Wrong IV length");
> + KASUMI_PMD_LOG(ERR, "Wrong IV length");
> return -EINVAL;
> }
>
> @@ -102,10 +103,11 @@ kasumi_set_session_parameters(struct
> kasumi_session *sess,
> if (auth_xform) {
> /* Only KASUMI F9 supported */
> if (auth_xform->auth.algo != RTE_CRYPTO_AUTH_KASUMI_F9)
> + KASUMI_PMD_LOG(ERR, "Unsupported
> authentication");
> return -ENOTSUP;
Missing braces, as there are two lines inside the if statement.
>
> if (auth_xform->auth.digest_length !=
next prev parent reply other threads:[~2018-06-27 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 5:23 Naga Suresh Somarowthu
2018-06-27 15:15 ` De Lara Guarch, Pablo
2018-06-27 15:38 ` De Lara Guarch, Pablo [this message]
2018-06-29 9:47 ` [dpdk-dev] [PATCH v2] crypto/kasumi: add dynamic logging Naga Suresh Somarowthu
2018-07-03 8:34 ` De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D8977F8DDC74@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=naga.sureshx.somarowthu@intel.com \
--cc=reshma.pattan@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).