From: Akhil Goyal <akhil.goyal@nxp.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] Fix handling of block size in qat for hash
Date: Tue, 18 Dec 2018 10:29:30 +0000 [thread overview]
Message-ID: <e3ba309e-bfd2-2097-27ff-f5a718a5642a@nxp.com> (raw)
In-Reply-To: <20181212195904.8160-1-arkadiuszx.kusztal@intel.com>
On 12/13/2018 1:29 AM, Arek Kusztal wrote:
> This patchset fixes invalid message which is caused by not
> entirely correct way of checking for block size.
>
> Arek Kusztal (3):
> crypto/qat: handle error msg of block size properly
> crypto/qat: fix message for CCM when setting unused counter
> crypto/qat: fix message for NULL algo setting unused counter
>
> drivers/crypto/qat/qat_sym_session.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
Applied to dpdk-next-crypto
Thanks
prev parent reply other threads:[~2018-12-18 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 19:59 Arek Kusztal
2018-12-12 19:59 ` [dpdk-dev] [PATCH 1/3] crypto/qat: handle error msg of block size properly Arek Kusztal
2018-12-17 12:12 ` Kovacevic, Marko
2018-12-12 19:59 ` [dpdk-dev] [PATCH 2/3] crypto/qat: fix message for CCM when setting unused counter Arek Kusztal
2018-12-14 14:23 ` Akhil Goyal
2018-12-14 14:39 ` Kusztal, ArkadiuszX
2018-12-17 12:16 ` Kovacevic, Marko
2018-12-12 19:59 ` [dpdk-dev] [PATCH 3/3] crypto/qat: fix message for NULL algo " Arek Kusztal
2018-12-13 23:01 ` [dpdk-dev] [PATCH 0/3] Fix handling of block size in qat for hash Trahe, Fiona
2018-12-17 12:15 ` Kovacevic, Marko
2018-12-18 10:29 ` Akhil Goyal [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=e3ba309e-bfd2-2097-27ff-f5a718a5642a@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).