From: Akhil Goyal <gakhil@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH 1/2] drivers/qat: fix wrong return value for invalid service
Date: Fri, 30 Jul 2021 19:18:25 +0000 [thread overview]
Message-ID: <CO6PR18MB448426273CA2A1EFCFC81E35D8EC9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210728161831.6807-2-arkadiuszx.kusztal@intel.com>
> Subject: [EXT] [PATCH 1/2] drivers/qat: fix wrong return value for invalid
> service
>
Title changed as " drivers: fix return value for QAT PMDs "
Please check ./devtools/check-git-log.sh before sending patch.
> Fix invalid value that is returned when asymmetric crypto
> or compression service is selected.
Description is also updated. Please check.
>
> Fixes: 8f393c4ffdc1 ("common/qat: support GEN4 devices")
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
Applied to dpdk-next-crypto
Braces across 'EFAULT' are not needed. I tried fixing it, but it is being
Used at many places. Please fix that in a separate patch.
next prev parent reply other threads:[~2021-07-30 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:18 [dpdk-dev] [PATCH 0/2] drivers/qat: fix handling of unsupported services Arek Kusztal
2021-07-28 16:18 ` [dpdk-dev] [PATCH 1/2] drivers/qat: fix wrong return value for invalid service Arek Kusztal
2021-07-29 8:58 ` Zhang, Roy Fan
2021-07-30 19:18 ` Akhil Goyal [this message]
2021-07-31 9:29 ` [dpdk-dev] [EXT] " Thomas Monjalon
2021-07-28 16:18 ` [dpdk-dev] [PATCH 2/2] crypto/qat: fix asymmetric crypto pmd create on gen3 Arek Kusztal
2021-07-29 8:57 ` Zhang, Roy Fan
2021-07-30 19:19 ` [dpdk-dev] [EXT] " 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=CO6PR18MB448426273CA2A1EFCFC81E35D8EC9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.