DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: thomas@monjalon.net, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH 1/2] devtools: remove ABI exception for baseband FFT
Date: Thu, 23 Nov 2023 10:36:14 +0100	[thread overview]
Message-ID: <643ad7d1-4368-4436-b987-3e549f8735c3@redhat.com> (raw)
In-Reply-To: <20231123085823.2218091-1-david.marchand@redhat.com>



On 11/23/23 09:58, David Marchand wrote:
> Those API are now stable.
> 
> Fixes: c96b519bd1c3 ("bbdev: promote some functions as stable")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>   devtools/libabigail.abignore | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore
> index 325f34e0b6..3ff51509de 100644
> --- a/devtools/libabigail.abignore
> +++ b/devtools/libabigail.abignore
> @@ -37,10 +37,6 @@
>           type_kind = enum
>           changed_enumerators = RTE_CRYPTO_ASYM_XFORM_ECPM, RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END
>   
> -; Ignore changes to bbdev FFT API which is experimental
> -[suppress_type]
> -        name = rte_bbdev_fft_op
> -
>   ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>   ; Temporary exceptions till next major ABI version ;
>   ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


      parent reply	other threads:[~2023-11-23  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  8:58 David Marchand
2023-11-23  8:58 ` [PATCH 2/2] devtools: remove ABI exception for crypto asym operations David Marchand
2023-11-24 19:39   ` [EXT] " Akhil Goyal
2023-11-27  7:35   ` David Marchand
2023-11-23  9:36 ` Maxime Coquelin [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=643ad7d1-4368-4436-b987-3e549f8735c3@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).