From: Declan Doherty <declan.doherty@intel.com>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>,
roy.fan.zhang@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] cryptodev: remove crypto operation status value
Date: Wed, 19 Jul 2017 15:00:01 +0100 [thread overview]
Message-ID: <8a1f6e9d-7c28-b7b6-7171-63b3b395d096@intel.com> (raw)
In-Reply-To: <1500305100-63460-1-git-send-email-kirill.rybalchenko@intel.com>
On 17/07/2017 4:25 PM, Kirill Rybalchenko wrote:
> Crypto operation status RTE_CRYPTO_OP_STATUS_ENQUEUED is removed
> from rte_crypto.h as it is not needed for crypto operation processing.
> This status value is redundant to RTE_CRYPTO_OP_STATUS_NOT_PROCESSED value
> and it was not intended to be part of public API.
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
> ---
...
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-19 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 15:25 Kirill Rybalchenko
2017-07-19 14:00 ` Declan Doherty [this message]
2017-07-19 14:35 ` De Lara Guarch, Pablo
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=8a1f6e9d-7c28-b7b6-7171-63b3b395d096@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=kirill.rybalchenko@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 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).