patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Jain, Deepak K" <deepak.k.jain@intel.com>,
	 "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
	"Chilikin, Andrey" <andrey.chilikin@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] app/testpmd: fix runtime dead code
Date: Fri, 13 Oct 2017 01:36:21 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810E94534@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <731b3c79-33e8-5a1e-1f2e-71d3b8011ce1@intel.com>



> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, October 13, 2017 3:28 AM
> To: Jastrzebski, MichalX K <michalx.k.jastrzebski@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; Jain, Deepak K <deepak.k.jain@intel.com>; Kulasek,
> TomaszX <tomaszx.kulasek@intel.com>; Chilikin, Andrey
> <andrey.chilikin@intel.com>; stable@dpdk.org
> Subject: Re: [dpdk-stable] [PATCH] app/testpmd: fix runtime dead code
> 
> On 9/29/2017 1:56 PM, Michal Jastrzebski wrote:
> > From: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> >
> > Coverity reports DEADCODE, as assumes that RTE_LIBRTE_I40E_PMD is
> > defined and function compiles entirely.
> > The fix is about to place printf function into #else branch of
> > conditional compilation, since it is known at compile time if i40e is
> > supported. No need to check it at runtime.
> 
> This is to highlight this is not supported other than defined PMD, and used like
> this in similar functions, I am for keeping this and marking coverity item as
> false positive.
> 
> Hi Jingjing,
> 
> What do you think, if you have strong opinion to get this, I will.
> 
> Thanks,
> ferruh
> 
> >

Hi, Ferruh

Checked other funcs called PMD specific API. And it seems all of them handle
That in the same way. So, to keep consistent, we may not need to apply this patch.

I agree with you to mark coverity item to no problem.

Thanks
Jingjing


      reply	other threads:[~2017-10-13  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 12:56 Michal Jastrzebski
2017-09-29 14:25 ` Wu, Jingjing
2017-10-12 19:28 ` Ferruh Yigit
2017-10-13  1:36   ` Wu, Jingjing [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=9BB6961774997848B5B42BEC655768F810E94534@SHSMSX103.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=andrey.chilikin@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=michalx.k.jastrzebski@intel.com \
    --cc=stable@dpdk.org \
    --cc=tomaszx.kulasek@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).