DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: thomas@monjalon.net, trix@redhat.com, hemant.agrawal@nxp.com,
	mingshan.zhang@intel.com, arun.joshi@intel.com,
	david.marchand@redhat.com, mdr@ashroe.eu,
	Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] [PATCH v1] bbdev: remove experimental tag from API
Date: Tue, 31 Aug 2021 09:25:29 -0700	[thread overview]
Message-ID: <1630427130-63903-1-git-send-email-nicolas.chautru@intel.com> (raw)

Sending again this change to move bbdev to stable API.
This was previously suggested last year https://patches.dpdk.org/project/dpdk/patch/1593213242-157394-2-git-send-email-nicolas.chautru@intel.com/
but there was request from community to wait another year to confirm formally this api is mature.
There has been no change for the last few years and we are receiving emails
from bots as these experimental tags are expiring now. 

Nicolas Chautru (1):
  bbdev: remove experimental tag from API

 doc/guides/rel_notes/release_21_11.rst |  2 ++
 lib/bbdev/rte_bbdev.h                  | 32 --------------------------------
 lib/bbdev/rte_bbdev_op.h               |  9 ---------
 lib/bbdev/rte_bbdev_pmd.h              |  7 -------
 lib/bbdev/version.map                  |  2 +-
 5 files changed, 3 insertions(+), 49 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2021-08-31 16:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 16:25 Nicolas Chautru [this message]
2021-08-31 16:25 ` Nicolas Chautru
2021-10-08 19:29   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-31 19:17     ` Akhil Goyal
2021-11-06  8:58       ` Thomas Monjalon
2021-08-31 16:38 ` [dpdk-dev] " David Marchand
2021-09-01  3:52   ` Hemant Agrawal
2021-09-01 11:14     ` Kinsella, Ray
2021-09-01 14:54       ` Chautru, Nicolas
2021-09-13 19:44         ` Maxime Coquelin
2021-09-14  3:13           ` Hemant Agrawal
2021-09-01 14:51     ` Chautru, Nicolas

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=1630427130-63903-1-git-send-email-nicolas.chautru@intel.com \
    --to=nicolas.chautru@intel.com \
    --cc=arun.joshi@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=mdr@ashroe.eu \
    --cc=mingshan.zhang@intel.com \
    --cc=thomas@monjalon.net \
    --cc=trix@redhat.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).