From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Jerin Jacob Kollanukkaran" <jerinj@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "Vangati, Narender" <narender.vangati@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: fix control flow issues
Date: Tue, 30 Apr 2019 17:08:44 +0000 [thread overview]
Message-ID: <BYAPR18MB242433B949AED6BD2CF36AFFC83A0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
Message-ID: <20190430170844.NA_xYgWanmFbxOw4RRO3pVIJfJStBADbQjE1I9-UDUc@z> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F60831F@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: Mcnamara, John <john.mcnamara@intel.com>
> Sent: Tuesday, April 30, 2019 3:14 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Gujjar, Abhinandan S
> <abhinandan.gujjar@intel.com>; jerin.jacob@caviumnetworks.com;
> dev@dpdk.org
> Cc: Vangati, Narender <narender.vangati@intel.com>
> Subject: [EXT] RE: [dpdk-dev] [PATCH] eventdev: fix control flow issues
> > > 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.
Thomas,
Could you merge this patch to avoid creating pull request for one patch.
>
> Thanks,
>
> John
>
next prev parent reply other threads:[~2019-04-30 17:08 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
2019-04-30 9:44 ` Mcnamara, John
2019-04-30 17:08 ` Jerin Jacob Kollanukkaran [this message]
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=BYAPR18MB242433B949AED6BD2CF36AFFC83A0@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=narender.vangati@intel.com \
--cc=thomas@monjalon.net \
/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).