> -----Original Message-----
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand
> Sent: Friday, January 11, 2019 1:15 PM
> To: dev@dpdk.org
> Cc: tho...@monjalon.net; Yigit, Ferruh <ferruh.yi...@intel.com>; 
> arybche...@solarflare.com
> Subject: [dpdk-dev] [PATCH] ethdev: declare tx prepare api as not experimental
> 
> The tx prepare api was introduced at a time when the experimental api
> tag mechanism did not exist yet and is missing the tag.
> However, this api has been there since 17.02 and did not suffer any
> change since its introduction.
> 
> Let's just remove the warning from the documentation.
> 
> Signed-off-by: David Marchand <david.march...@redhat.com>
> ---
> This has been caught while reviewing the tso support in ovs.
> There seems to be a lot of other incorrectly documentated apis like
> this...
> I will see if I can find an easy way to identify them.
> ---
>  lib/librte_ethdev/rte_ethdev.h | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
> index 1960f3a..76266ad 100644
> --- a/lib/librte_ethdev/rte_ethdev.h
> +++ b/lib/librte_ethdev/rte_ethdev.h
> @@ -4159,9 +4159,6 @@ static inline int rte_eth_tx_descriptor_status(uint16_t 
> port_id,
>  }
> 
>  /**
> - * @warning
> - * @b EXPERIMENTAL: this API may change without prior notice
> - *
>   * Process a burst of output packets on a transmit queue of an Ethernet 
> device.
>   *
>   * The rte_eth_tx_prepare() function is invoked to prepare output packets to 
> be
> --

Acked-by: Konstantin Ananyev <konstantin.anan...@intel.com>

> 1.8.3.1

Reply via email to