From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Jozwiak, TomaszX" <tomaszx.jozwiak@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] compress/qat: fix status return on error building request
Date: Fri, 14 Dec 2018 18:48:13 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896A2346@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1544786371-29799-2-git-send-email-tomaszx.jozwiak@intel.com>
> -----Original Message-----
> From: Jozwiak, TomaszX
> Sent: Friday, December 14, 2018 4:20 AM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; Jozwiak, TomaszX
> <tomaszx.jozwiak@intel.com>; akhil.goyal@nxp.com; stable@dpdk.org
> Subject: [PATCH] compress/qat: fix status return on error building request
>
> This patch fixes error status which should be set inside
> qat_comp_build_request function in case any errors are detected.
> In these cases op.status is set to
> RTE_COMP_OP_STATUS_INVALID_ARGS to help application debug.
>
> Fixes: 1947bd18580b ("compress/qat: support scatter-gather buffers")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2018-12-14 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 11:19 [dpdk-dev] [PATCH] common/qat: revert fix for invalid response from firmware Tomasz Jozwiak
2018-12-14 11:19 ` [dpdk-dev] [PATCH] compress/qat: fix status return on error building request Tomasz Jozwiak
2018-12-14 18:48 ` Trahe, Fiona [this message]
2018-12-18 10:32 ` Akhil Goyal
2019-01-09 22:43 ` De Lara Guarch, Pablo
2018-12-14 18:47 ` [dpdk-dev] [PATCH] common/qat: revert fix for invalid response from firmware Trahe, Fiona
2018-12-18 10:31 ` Akhil Goyal
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=348A99DA5F5B7549AA880327E580B435896A2346@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=tomaszx.jozwiak@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).