DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ip_frag: promote APIs to stable
Date: Wed, 20 Oct 2021 10:39:52 +0100	[thread overview]
Message-ID: <7cac7db3-838e-2370-6d9d-c460193b035d@ashroe.eu> (raw)
In-Reply-To: <20211018153619.31736-1-konstantin.ananyev@intel.com>



On 18/10/2021 16:36, Konstantin Ananyev wrote:
> 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 -
>   lib/ip_frag/version.map   | 7 +------
>   2 files changed, 1 insertion(+), 7 deletions(-)
> 
> diff --git a/lib/ip_frag/rte_ip_frag.h b/lib/ip_frag/rte_ip_frag.h
> index 08555fde6a..d856f87e6c 100644
> --- a/lib/ip_frag/rte_ip_frag.h
> +++ b/lib/ip_frag/rte_ip_frag.h
> @@ -326,7 +326,6 @@ rte_ip_frag_table_statistics_dump(FILE * f, const struct rte_ip_frag_tbl *tbl);
>    * @param tms
>    *   Current timestamp
>    */
> -__rte_experimental
>   void
>   rte_frag_table_del_expired_entries(struct rte_ip_frag_tbl *tbl,
>   	struct rte_ip_frag_death_row *dr, uint64_t tms);
> diff --git a/lib/ip_frag/version.map b/lib/ip_frag/version.map
> index 33f231fb31..990384b536 100644
> --- a/lib/ip_frag/version.map
> +++ b/lib/ip_frag/version.map
> @@ -8,13 +8,8 @@ DPDK_22 {
>   	rte_ipv4_frag_reassemble_packet;
>   	rte_ipv4_fragment_packet;
>   	rte_ipv6_frag_reassemble_packet;
> +	rte_frag_table_del_expired_entries;

isn't f before i?

>   	rte_ipv6_fragment_packet;
>   
>   	local: *;
>   };
> -
> -EXPERIMENTAL {
> -	global:
> -
> -	rte_frag_table_del_expired_entries;
> -};
> 

Ray K

  reply	other threads:[~2021-10-20  9:40 UTC|newest]

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

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=7cac7db3-838e-2370-6d9d-c460193b035d@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.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).