DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] cryptodev: Remove EXPERIMENTAL label
Date: Thu, 7 Apr 2016 11:06:09 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43588FC7B9B@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1460026585-30674-1-git-send-email-fiona.trahe@intel.com>

Sorry for spam, accidental resend

> -----Original Message-----
> From: Trahe, Fiona
> Sent: Thursday, April 07, 2016 11:56 AM
> To: dev@dpdk.org
> Cc: Doherty, Declan; Trahe, Fiona
> Subject: [PATCH v2] cryptodev: Remove EXPERIMENTAL label
> 
> The cryptodev API was introduced in the DPDK 2.2 release.
> Since then it has
>  - been reviewed and iterated for the DPDK 16.04 release
>  - had extensive use by the l2fwd-crypto app,
> 			the ipsec-secgw example app,
> 			the test app.
> We believe it is now stable and the EXPERIMENTAL label should be removed.
> 
> v2:
> - remove extra empty line
> 
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
>  MAINTAINERS                          | 2 +-
>  config/common_base                   | 1 -
>  lib/librte_cryptodev/rte_cryptodev.h | 3 ---
>  3 files changed, 1 insertion(+), 5 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 85d72ca..a7570cd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -231,7 +231,7 @@ M: Thomas Monjalon <thomas.monjalon@6wind.com>
>  F: lib/librte_ether/
>  F: scripts/test-null.sh
> 
> -Crypto API - EXPERIMENTAL
> +Crypto API
>  M: Declan Doherty <declan.doherty@intel.com>
>  F: lib/librte_cryptodev/
>  F: app/test/test_cryptodev*
> diff --git a/config/common_base b/config/common_base index
> abd6a64..0124e86 100644
> --- a/config/common_base
> +++ b/config/common_base
> @@ -327,7 +327,6 @@ CONFIG_RTE_PMD_PACKET_PREFETCH=y
> 
>  #
>  # Compile generic crypto device library -# EXPERIMENTAL: API may change
> without prior notice  #  CONFIG_RTE_LIBRTE_CRYPTODEV=y
> CONFIG_RTE_LIBRTE_CRYPTODEV_DEBUG=n
> diff --git a/lib/librte_cryptodev/rte_cryptodev.h
> b/lib/librte_cryptodev/rte_cryptodev.h
> index 568ffbb..d47f1e8 100644
> --- a/lib/librte_cryptodev/rte_cryptodev.h
> +++ b/lib/librte_cryptodev/rte_cryptodev.h
> @@ -39,9 +39,6 @@
>   *
>   * Defines RTE Crypto Device APIs for the provisioning of cipher and
>   * authentication operations.
> - *
> - * @b EXPERIMENTAL: this API may change without prior notice
> - *
>   */
> 
>  #ifdef __cplusplus
> --
> 2.1.0

      reply	other threads:[~2016-04-07 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 10:56 Fiona Trahe
2016-04-07 11:06 ` Trahe, Fiona [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=348A99DA5F5B7549AA880327E580B43588FC7B9B@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@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).