DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
	"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Vangati, Narender" <narender.vangati@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: fix control flow issues
Date: Tue, 30 Apr 2019 09:44:01 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F60831F@IRSMSX103.ger.corp.intel.com> (raw)
Message-ID: <20190430094401.oldDrofhNEm18yWyxPi9NLeAyABuBVvzCAwXDCPN9eM@z> (raw)
In-Reply-To: <BYAPR18MB242432CB5EF0DFD3D3CCD699C83E0@BYAPR18MB2424.namprd18.prod.outlook.com>

> > Coverity issue: 279439 Dereference null return value Coverity issue:
> > 279446 Logically dead code Coverity issue: 279450 Logically dead code
> Coverity issue:
> > 279462 Logically dead code
> > Fixes: 7901eac3409 ("eventdev: add crypto adapter implementation")
> 
> Cc: stable@dpdk.org
> 
> >
> > Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Hi Jerin,

Can you apply this patch for RC3. It potentially fixes 4 coverity defcts.

Thanks,

John



  parent reply	other threads:[~2019-04-30  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 16:34 Abhinandan Gujjar
2019-04-24 16:34 ` Abhinandan Gujjar
2019-04-26  8:00 ` Jerin Jacob Kollanukkaran
2019-04-26  8:00   ` Jerin Jacob Kollanukkaran
2019-04-30  9:44   ` Mcnamara, John [this message]
2019-04-30  9:44     ` Mcnamara, John
2019-04-30 17:08     ` Jerin Jacob Kollanukkaran
2019-04-30 17:08       ` Jerin Jacob Kollanukkaran
2019-05-01 21:11   ` Thomas Monjalon
2019-05-01 21:11     ` Thomas Monjalon

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=B27915DBBA3421428155699D51E4CFE23F60831F@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jerinj@marvell.com \
    --cc=narender.vangati@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).