From: Akhil Goyal <akhil.goyal@nxp.com>
To: Junxiao Shi <git@mail1.yoursunny.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] crypto: fix element size for undefined crypto op
Date: Wed, 10 Oct 2018 10:56:57 +0530 [thread overview]
Message-ID: <d607a366-2745-ee21-e440-305a92a16c05@nxp.com> (raw)
In-Reply-To: <49c058ab-e1c1-32be-120f-4878addd61e8@nxp.com>
On 10/10/2018 10:40 AM, Akhil Goyal wrote:
>
>
> On 10/9/2018 7:46 PM, Junxiao Shi wrote:
>> The documentation of rte_crypto_op_pool_create indicates that
>> specifying RTE_CRYPTO_OP_TYPE_UNDEFINED would create a pool that
>> supports all operation types. This change makes the code
>> consistent with documentation.
>>
>> Fixes: c0f87eb5252b ("cryptodev: change burst API to be crypto op
>> oriented")
>>
>> Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com>
>> ---
>>
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied to dpdk-next-crypto
modified the patch title to
crypto: fix pool element size for undefined crypto op
Thanks
prev parent reply other threads:[~2018-10-10 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 14:16 Junxiao Shi
2018-10-10 5:10 ` Akhil Goyal
2018-10-10 5:26 ` 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=d607a366-2745-ee21-e440-305a92a16c05@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=git@mail1.yoursunny.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).