From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: Remove EXPERIMENTAL label
Date: Wed, 6 Apr 2016 16:46:18 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43588FC71B6@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <8588938.YlbkXjqJbI@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, April 06, 2016 5:37 PM
> To: Trahe, Fiona
> Cc: dev@dpdk.org; Doherty, Declan
> Subject: Re: [dpdk-dev] [PATCH] cryptodev: Remove EXPERIMENTAL label
>
> 2016-04-06 12:05, Fiona Trahe:
> > 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.
>
> I thought it was a good idea to use a dpdk_ prefix in this new "stable" lib, but it
> appears that almost everybody is against having a mix of prefixes.
>
> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
> > v2:
>
> The v2 is missing in the title (option -v2 in git).
Sorry :(
Do you want me to resend with updated subject?
next prev parent reply other threads:[~2016-04-06 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 7:53 Fiona Trahe
2016-04-05 8:47 ` Thomas Monjalon
2016-04-05 9:48 ` Trahe, Fiona
2016-04-05 10:11 ` Thomas Monjalon
2016-04-05 13:29 ` [dpdk-dev] Change new libraries to have dpdk_ prefix instead of rte_ Declan Doherty
2016-04-05 14:03 ` Ananyev, Konstantin
2016-04-05 14:22 ` Thomas Monjalon
2016-04-05 16:45 ` Wiles, Keith
2016-04-06 11:05 ` [dpdk-dev] [PATCH] cryptodev: Remove EXPERIMENTAL label Fiona Trahe
2016-04-06 16:37 ` Thomas Monjalon
2016-04-06 16:46 ` Trahe, Fiona [this message]
2016-04-06 16:49 ` Thomas Monjalon
2016-04-06 17:07 ` Thomas Monjalon
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=348A99DA5F5B7549AA880327E580B43588FC71B6@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).