From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Kozak, KubaX" <kubax.kozak@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Kozak, KubaX" <kubax.kozak@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix total_ops value validation
Date: Thu, 9 Feb 2017 23:25:49 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476D7C54@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897476D7C16@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Thursday, February 09, 2017 11:18 PM
> To: Kozak, KubaX; Doherty, Declan
> Cc: dev@dpdk.org; Kozak, KubaX
> Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix total_ops value
> validation
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kuba Kozak
> > Sent: Tuesday, February 07, 2017 12:20 PM
> > To: Doherty, Declan
> > Cc: dev@dpdk.org; Kozak, KubaX
> > Subject: [dpdk-dev] [PATCH] app/crypto-perf: fix total_ops value
> validation
> >
> > Added total_ops value validation in parse_total_ops() function.
> >
> > Coverity issue: 141070
> >
> > Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test
> > application")
> >
> > Signed-off-by: Kuba Kozak <kubax.kozak@intel.com>
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-02-09 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 12:20 Kuba Kozak
2017-02-09 23:17 ` De Lara Guarch, Pablo
2017-02-09 23:25 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D897476D7C54@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=kubax.kozak@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).