All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, mdr@ashroe.eu
Subject: Re: [dpdk-dev] [PATCH v2] ip_frag: promote APIs to stable
Date: Thu, 04 Nov 2021 19:24:27 +0100	[thread overview]
Message-ID: <1931385.obRyEIEG8d@thomas> (raw)
In-Reply-To: <20211028115100.10556-1-konstantin.ananyev@intel.com>

28/10/2021 13:51, Konstantin Ananyev:
> Promote rte_frag_table_del_expired_entries() function to stable.
> It was around for few years by now without any changes.
> 
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
>  lib/ip_frag/rte_ip_frag.h | 1 -

In general, the namespace in this file is wrong.
A lot of structs and enum don't have the correct name prefix.


> --- a/lib/ip_frag/version.map
> +++ b/lib/ip_frag/version.map
> @@ -1,6 +1,7 @@
>  DPDK_22 {
>  	global:
>  
> +	rte_frag_table_del_expired_entries;

It seems that the right name should be rte_ip_frag_table_del_expired_entries.

>  	rte_ip_frag_free_death_row;
>  	rte_ip_frag_table_create;
>  	rte_ip_frag_table_destroy;
> @@ -12,9 +13,3 @@ DPDK_22 {
>  
>  	local: *;
>  };
> -
> -EXPERIMENTAL {
> -	global:
> -
> -	rte_frag_table_del_expired_entries;
> -};

We could keep this name as experimental during an expiration period.



      reply	other threads:[~2021-11-04 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 15:36 [dpdk-dev] [PATCH] ip_frag: promote APIs to stable Konstantin Ananyev
2021-10-20  9:39 ` Kinsella, Ray
2021-10-28 11:51 ` [dpdk-dev] [PATCH v2] " Konstantin Ananyev
2021-11-04 18:24   ` Thomas Monjalon [this message]

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=1931385.obRyEIEG8d@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.