DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 00/14] eal: mark older API's as stable
Date: Tue, 14 Nov 2023 14:10:42 +0100	[thread overview]
Message-ID: <CAJFAV8wqaQLsCW-+K=H=6oj9JVaVCiQkCipTY07Jw6B=EvoF2g@mail.gmail.com> (raw)
In-Reply-To: <20231020214119.255491-1-stephen@networkplumber.org>

On Fri, Oct 20, 2023 at 11:41 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> About 80 function in EAL were marked experimental
> and should have been made stable by now.
>
> v2 - rebase and fix some bits in wrong patch
>
> Stephen Hemminger (14):
>   eal: make bitops a stable API
>   eal: mark rte_dev API's as stable
>   eal: make rte_class API's stable
>   eal: make rte_drand a stable API
>   eal: make rte_service_lcore_may_be_active stable
>   eal: make rte_devargs_reset stable
>   eal: make pflock API stable
>   eal: make seqcount and seqlock stable
>   eal: mark rte_intr_XXX API's as stable
>   eal: mark rte_atomic128_cmp_exchange as stable
>   eal: mark rte_power API's stable
>   eal: mark rte_eal_vfio_get_token stable
>   eal: mark rte_vect simd bandwidth API as stable
>   eal: make rte_version API's stable
>
>  lib/eal/arm/include/rte_atomic_64.h           |  1 -
>  lib/eal/include/generic/rte_atomic.h          |  1 -
>  .../include/generic/rte_power_intrinsics.h    | 16 ----
>  lib/eal/include/generic/rte_vect.h            |  8 --
>  lib/eal/include/rte_bitmap.h                  |  8 --
>  lib/eal/include/rte_bitops.h                  | 40 --------
>  lib/eal/include/rte_class.h                   |  4 -
>  lib/eal/include/rte_dev.h                     | 32 -------
>  lib/eal/include/rte_devargs.h                 |  1 -
>  lib/eal/include/rte_eal.h                     |  4 -
>  lib/eal/include/rte_interrupts.h              | 28 ------
>  lib/eal/include/rte_pflock.h                  | 20 ----
>  lib/eal/include/rte_random.h                  |  4 -
>  lib/eal/include/rte_seqcount.h                | 23 -----
>  lib/eal/include/rte_seqlock.h                 | 21 ----
>  lib/eal/include/rte_service.h                 |  1 -
>  lib/eal/include/rte_version.h                 |  6 --
>  lib/eal/version.map                           | 96 ++++++++-----------
>  lib/eal/x86/include/rte_atomic_64.h           |  1 -
>  19 files changed, 38 insertions(+), 277 deletions(-)

Series applied.
Thanks.


-- 
David Marchand


      parent reply	other threads:[~2023-11-14 13:11 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 16:42 [PATCH 00/15] eal: mark older API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 01/15] eal: make bitops a stable API Stephen Hemminger
2023-08-09 17:58   ` Tyler Retzlaff
2023-08-09 20:07     ` Stephen Hemminger
2023-08-09 21:59       ` Tyler Retzlaff
2023-08-09 16:42 ` [PATCH 02/15] eal: mark rte_dev API's as stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 03/15] eal: make rte_class API's stable Stephen Hemminger
2023-08-09 16:42 ` [PATCH 04/15] eal: make rte_version_XXX " Stephen Hemminger
2023-08-10  8:24   ` Bruce Richardson
2023-08-09 16:42 ` [PATCH 05/15] eal: make rte_drand a stable API Stephen Hemminger
2023-08-09 16:42 ` [PATCH 06/15] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-08-10  9:08   ` Van Haaren, Harry
2023-08-09 16:42 ` [PATCH 07/15] eal: make rte_devargs_reset stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 08/15] eal: make pflock API stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 09/15] eal: make seqcount and seqlock stable Stephen Hemminger
2023-08-09 19:47   ` Mattias Rönnblom
2023-08-09 16:43 ` [PATCH 10/15] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-08-09 16:43 ` [PATCH 11/15] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-08-09 17:50   ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 12/15] eal: make most rte_thread API's stable Stephen Hemminger
2023-08-09 17:53   ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 13/15] eal: mark rte_power " Stephen Hemminger
2023-08-09 16:43 ` [PATCH 14/15] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-08-09 17:55   ` Tyler Retzlaff
2023-08-09 16:43 ` [PATCH 15/15] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-18 19:29 ` [PATCH 00/15] eal: mark older API's stable David Marchand
2023-10-20 21:41 ` [PATCH v2 00/14] eal: mark older API's as stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 01/14] eal: make bitops a stable API Stephen Hemminger
2023-10-23  2:31     ` Joyce Kong
2023-10-20 21:41   ` [PATCH v2 02/14] eal: mark rte_dev API's as stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 03/14] eal: make rte_class API's stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 04/14] eal: make rte_drand a stable API Stephen Hemminger
2023-10-23 16:12     ` Mattias Rönnblom
2023-10-20 21:41   ` [PATCH v2 05/14] eal: make rte_service_lcore_may_be_active stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 06/14] eal: make rte_devargs_reset stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 07/14] eal: make pflock API stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 08/14] eal: make seqcount and seqlock stable Stephen Hemminger
2023-10-23 16:14     ` Mattias Rönnblom
2023-10-20 21:41   ` [PATCH v2 09/14] eal: mark rte_intr_XXX API's as stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 10/14] eal: mark rte_atomic128_cmp_exchange " Stephen Hemminger
2023-10-23  3:00     ` Ruifeng Wang
2023-10-20 21:41   ` [PATCH v2 11/14] eal: mark rte_power API's stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 12/14] eal: mark rte_eal_vfio_get_token stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 13/14] eal: mark rte_vect simd bandwidth API as stable Stephen Hemminger
2023-10-20 21:41   ` [PATCH v2 14/14] eal: make rte_version API's stable Stephen Hemminger
2023-10-23  9:13   ` [PATCH v2 00/14] eal: mark older API's as stable Bruce Richardson
2023-11-14 13:10   ` David Marchand [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='CAJFAV8wqaQLsCW-+K=H=6oj9JVaVCiQkCipTY07Jw6B=EvoF2g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).