All of lore.kernel.org
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>
Subject: Re: [PATCH] lib/cryptodev: remove RTE_LIBRTE_CRYPTODEV_DEBUG
Date: Wed, 27 Jun 2018 16:36:57 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8DDE28@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <7c8dc199-9d02-e23a-05e1-0f0666149275@nxp.com>

Hi Jananee,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Akhil Goyal
> Sent: Thursday, June 21, 2018 3:13 PM
> To: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>;
> dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Pattan, Reshma
> <reshma.pattan@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] lib/cryptodev: remove
> RTE_LIBRTE_CRYPTODEV_DEBUG
> 
> Please remove lib from subject also.
> 
> 
> On 6/21/2018 7:41 PM, Akhil Goyal wrote:
> > Hi Jananee,
> >
> >
> > On 6/12/2018 12:08 PM, Jananee Parthasarathy wrote:
> >> For librte_cryptodev dynamic logging, conditional compilation of
> >> debug logs would not be required anymore.
> >
> > I believe this shall also be removed from config/common_base and
> > lib/librte_eal/common/include/rte_dev.h as nobody is using it.
> >

Could you make these changes soon?

Thanks,
Pablo

  reply	other threads:[~2018-06-27 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  6:38 [PATCH] lib/cryptodev: remove RTE_LIBRTE_CRYPTODEV_DEBUG Jananee Parthasarathy
2018-06-21 14:11 ` Akhil Goyal
2018-06-21 14:12   ` Akhil Goyal
2018-06-27 16:36     ` De Lara Guarch, Pablo [this message]
2018-07-02 12:30 ` [PATCH v2] cryptodev: " Jananee Parthasarathy
2018-07-02 15:51   ` 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=E115CCD9D858EF4F90C690B0DCB4D8977F8DDE28@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.