From: Thomas Monjalon <thomas@monjalon.net>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
Akhil Goyal <gakhil@marvell.com>
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: Sat, 31 Jul 2021 11:29:00 +0200 [thread overview]
Message-ID: <2065297.4XKkAc0obF@thomas> (raw)
In-Reply-To: <CO6PR18MB448426273CA2A1EFCFC81E35D8EC9@CO6PR18MB4484.namprd18.prod.outlook.com>
30/07/2021 21:18, Akhil Goyal:
> > 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.
There are not parenthesis for every returns,
so I will remove those introduced by this patch.
next prev parent reply other threads:[~2021-07-31 9:38 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 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-31 9:29 ` Thomas Monjalon [this message]
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=2065297.4XKkAc0obF@thomas \
--to=thomas@monjalon.net \
--cc=arkadiuszx.kusztal@intel.com \
--cc=fiona.trahe@intel.com \
--cc=gakhil@marvell.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 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).