dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Govindarajan, LavanyaX" <lavanyax.govindarajan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
	"Govindarajan, LavanyaX" <lavanyax.govindarajan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/iavf: move debug dump desc flag to config	file
Date: Tue, 18 Jun 2019 14:22:20 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611533A7D1D@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1560172058-10742-1-git-send-email-lavanyax.govindarajan@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lavanya
> Govindarajan
> Sent: Monday, June 10, 2019 9:08 PM
> To: dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>;
> Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>;
> Govindarajan, LavanyaX <lavanyax.govindarajan@intel.com>
> Subject: [dpdk-dev] [PATCH] net/iavf: move debug dump desc flag to config
> file
> 
> DEBUG_DUMP_DESC flag is commented out in IAVF Makefile and to enable it
> user needs to edit the Makefile. It is felt that this method is not good. Hence
> removing this flag from IAVF makefile and adding a flag
> CONFIG_RTE_LIBRTE_IAVF_DEBUG_DUMP_DESC to config/common_base.
> 
> Signed-off-by: Lavanya Govindarajan <lavanyax.govindarajan@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

      reply	other threads:[~2019-06-18 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 13:07 [dpdk-dev] [PATCH] net/iavf: move debug dump desc flag to config file Lavanya Govindarajan
2019-06-18 14:22 ` Zhang, Qi Z [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=039ED4275CED7440929022BC67E70611533A7D1D@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=lavanyax.govindarajan@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=wenzhuo.lu@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).