DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Chenbo Xia <chenbo.xia@intel.com>
Cc: dev@dpdk.org, maxime.coquelin@redhat.com, amorenoz@redhat.com,
	stephen@networkplumber.org, ferruh.yigit@intel.com,
	bruce.richardson@intel.com, konstantin.ananyev@intel.com,
	ktraynor@redhat.com, jerinjacobk@gmail.com
Subject: Re: [dpdk-dev] [PATCH v2] vhost: announce experimental tag removal of vhost APIs
Date: Sat, 07 Aug 2021 19:44:36 +0200	[thread overview]
Message-ID: <6387994.FJyCi8zBdz@thomas> (raw)
In-Reply-To: <20210730082416.10741-1-chenbo.xia@intel.com>

30/07/2021 10:24, Chenbo Xia:
> This patch announces the experimental tag removal of 10 vhost APIs,
> which have been experimental for more than 2 years. All APIs could
> be made stable in DPDK 21.11.
> 
> Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> +* 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`` APIs will be removed and the
> +  APIs will be made stable in DPDK 21.11.

Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Marvin Liu <yong.liu@intel.com>

"APIs" is replaced with "API functions" for correctness.

Applied, thanks.



  parent reply	other threads:[~2021-08-07 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  8:19 [dpdk-dev] [PATCH] " Chenbo Xia
2021-07-30  8:24 ` [dpdk-dev] [PATCH v2] " Chenbo Xia
2021-08-03  7:54   ` Zhang, Roy Fan
2021-08-06  8:25   ` Liu, Yong
2021-08-07 17:44   ` Thomas Monjalon [this message]
2021-08-03  7:47 ` [dpdk-dev] [PATCH] " Zhang, Roy Fan

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=6387994.FJyCi8zBdz@thomas \
    --to=thomas@monjalon.net \
    --cc=amorenoz@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=stephen@networkplumber.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).