From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "dpdk-up@NXP1.onmicrosoft.com" <dpdk-up@NXP1.onmicrosoft.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] crypto/dpaa2_sec: improve error handling
Date: Tue, 17 Apr 2018 14:42:58 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CCD656D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <8426f0fe-9746-b6d3-784c-fea91beae6ec@nxp.com>
> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Monday, April 16, 2018 10:15 AM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; dev@dpdk.org
> Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; dpdk-
> up@NXP1.onmicrosoft.com
> Subject: Re: [PATCH 2/2] crypto/dpaa2_sec: improve error handling
>
> On 4/5/2018 2:05 PM, Hemant Agrawal wrote:
> > From: Sunil Kumar Kori <sunil.kori@nxp.com>
> >
> > Fixed as reported by NXP's internal coverity.
> > Also part of dpdk coverity.
> >
> > Coverity issue: 268331
> > Coverity issue: 268333
> >
> > Signed-off-by: Sunil Kumar Kori <sunil.kori@nxp.com>
> > ---
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Added Fixes line and CC'd stable.
Applied to dpdk-next-crypto.
Thanks,
Pablo
next prev parent reply other threads:[~2018-04-17 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 8:35 [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: improve the error checking Hemant Agrawal
2018-04-05 8:35 ` [dpdk-dev] [PATCH 2/2] crypto/dpaa2_sec: improve error handling Hemant Agrawal
2018-04-16 9:14 ` Akhil Goyal
2018-04-17 14:42 ` De Lara Guarch, Pablo [this message]
2018-04-16 9:13 ` [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: improve the error checking Akhil Goyal
2018-04-17 14:42 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CCD656D@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=dpdk-up@NXP1.onmicrosoft.com \
--cc=hemant.agrawal@nxp.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).