From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mokhtar, Amr" <amr.mokhtar@intel.com>,
"Chalupnik, KamilX" <kamilx.chalupnik@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] app/testbbdev: fix unchecked return value
Date: Thu, 17 May 2018 16:15:03 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CD0D3A3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <3D3765A8CDB52A4C8B410430AA19CB236ECDD894@IRSMSX104.ger.corp.intel.com>
> -----Original Message-----
> From: Mokhtar, Amr
> Sent: Thursday, May 17, 2018 1:41 PM
> To: Chalupnik, KamilX <kamilx.chalupnik@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] app/testbbdev: fix unchecked return value
>
>
> > -----Original Message-----
> > From: Chalupnik, KamilX
> > Sent: Wednesday 16 May 2018 14:57
> > To: Mokhtar, Amr <amr.mokhtar@intel.com>; De Lara Guarch, Pablo
> > <pablo.de.lara.guarch@intel.com>
> > Cc: dev@dpdk.org; Chalupnik, KamilX <kamilx.chalupnik@intel.com>
> > Subject: [PATCH] app/testbbdev: fix unchecked return value
> >
> > Fixing CHECKED_RETURN issue by checking values returned by
> > rte_bbdev_dec_op_alloc_bulk and rte_bbdev_enc_op_alloc_bulk functions.
> >
> > Fixes: f714a18885a6 ("app/testbbdev: add test application for bbdev")
> > Coverity issue: 279447, 279456
Added Cc: stable@dpdk.org
> >
> > Signed-off-by: Kamil Chalupnik <kamilx.chalupnik@intel.com>
>
> Acked-by: Amr Mokhtar <amr.mokhtar@intel.com>
Applied to dpdk-next-crypto.
By the way, could you change your author name to Kamil Chalupnik,
to match your "Signed-off-by:" line.
Thanks,
Pablo
parent reply other threads:[~2018-05-17 16:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3D3765A8CDB52A4C8B410430AA19CB236ECDD894@IRSMSX104.ger.corp.intel.com>]
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=E115CCD9D858EF4F90C690B0DCB4D8976CD0D3A3@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=amr.mokhtar@intel.com \
--cc=dev@dpdk.org \
--cc=kamilx.chalupnik@intel.com \
--cc=stable@dpdk.org \
/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).