DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Kevin Traynor <ktraynor@redhat.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH] doc: remove deprecation notice for vhost
Date: Wed, 3 Nov 2021 05:25:03 +0000	[thread overview]
Message-ID: <SN6PR11MB3504625DA2AC3EEB6E2AF1569C8C9@SN6PR11MB3504.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211103050026.41516-1-chenbo.xia@intel.com>

Hi,

I notice that from the start, I should not send the notice.. as the abi policy said:

For removing the experimental tag associated with an API, deprecation notice is not required.

Sorry for the mistake.
/Chenbo

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Chenbo Xia
> Sent: Wednesday, November 3, 2021 1:00 PM
> To: dev@dpdk.org
> Cc: Ray Kinsella <mdr@ashroe.eu>; Kevin Traynor <ktraynor@redhat.com>; Maxime
> Coquelin <maxime.coquelin@redhat.com>
> Subject: [dpdk-dev] [PATCH] doc: remove deprecation notice for vhost
> 
> Ten vhost APIs were announced to be stable and promoted in below
> commit, so remove the related deprecation notice.
> 
> Fixes: 945ef8a04098 ("vhost: promote some APIs to stable")
> 
> Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
> Reported-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 4366015b01..4f7e95f05f 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -114,14 +114,6 @@ Deprecation Notices
>  * vhost: rename ``struct vhost_device_ops`` to ``struct
> rte_vhost_device_ops``
>    in DPDK v21.11.
> 
> -* vhost: The experimental tags of ``rte_vhost_driver_get_protocol_features``,
> -  ``rte_vhost_driver_get_queue_num``, ``rte_vhost_crypto_create``,
> -  ``rte_vhost_crypto_free``, ``rte_vhost_crypto_fetch_requests``,
> -  ``rte_vhost_crypto_finalize_requests``, ``rte_vhost_crypto_set_zero_copy``,
> -  ``rte_vhost_va_from_guest_pa``, ``rte_vhost_extern_callback_register``,
> -  and ``rte_vhost_driver_set_protocol_features`` functions will be removed
> -  and the API functions will be made stable in DPDK 21.11.
> -
>  * cryptodev: Hide structures ``rte_cryptodev_sym_session`` and
>    ``rte_cryptodev_asym_session`` to remove unnecessary indirection between
>    session and the private data of session. An opaque pointer can be exposed
> --
> 2.17.1


  reply	other threads:[~2021-11-03  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  5:00 Chenbo Xia
2021-11-03  5:25 ` Xia, Chenbo [this message]
2021-11-03  7:03   ` David Marchand
2021-11-03  8:08 ` Maxime Coquelin
2021-11-03 13:47 ` Maxime Coquelin

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=SN6PR11MB3504625DA2AC3EEB6E2AF1569C8C9@SN6PR11MB3504.namprd11.prod.outlook.com \
    --to=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mdr@ashroe.eu \
    /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).