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>,
"Chaitanya Babu, TalluriX" <tallurix.chaitanya.babu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/aesni_gcm: add dynamic logging to aesni_gcm
Date: Wed, 27 Jun 2018 15:13:22 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8DDBCF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1528786244-24821-1-git-send-email-naga.sureshx.somarowthu@intel.com>
Hi Naga/Talluri,
> -----Original Message-----
> From: Somarowthu, Naga SureshX
> Sent: Tuesday, June 12, 2018 7:51 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Pattan, Reshma
> <reshma.pattan@intel.com>; Chaitanya Babu, TalluriX
> <tallurix.chaitanya.babu@intel.com>
> Subject: [PATCH] crypto/aesni_gcm: add dynamic logging to aesni_gcm
>
> From: tchaitax <tallurix.chaitanya.babu@intel.com>
>
> 1.added new logtype for aesni_gcm driver.
> 2.registered new logtype.
> 3.GCM_LOG_ERR and CDEV_LOG_ERR are replaced with
> new logtype name AESNI_GCM_PMD_LOG.
>
> Signed-off-by: Talluri Chaitanya <tallurix.chaitanya.babu@intel.com>
> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
Could you make the following changes?
- Change the macro to AESNI_GCM_LOG, to make it shorter.
- Change title to: crypto/aesni_gcm: add dynamic logging
- Change the author name to "Talluri Chaitanya"
- Remove unused "CONFIG_RTE_LIBRTE_PMD_AESNI_GCM_DEBUG=n"
from config file.
- Set log level of the new type to INFO (see isal_compress_pmd.c)
Thanks,
Pablo
next prev parent reply other threads:[~2018-06-27 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 6:50 Naga Suresh Somarowthu
2018-06-27 15:13 ` De Lara Guarch, Pablo [this message]
2018-06-28 14:47 ` [dpdk-dev] [PATCH v2] crypto/aesni_gcm: add dynamic logging Naga Suresh Somarowthu
2018-07-03 8:37 ` 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=E115CCD9D858EF4F90C690B0DCB4D8977F8DDBCF@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 \
--cc=tallurix.chaitanya.babu@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).