patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: stable@dpdk.org
Cc: bluca@debian.org, arkadiuszx.kusztal@intel.com,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH 21.11] build: suppress rte_crypto_asym_op abi check
Date: Wed, 16 Mar 2022 16:08:12 +0000	[thread overview]
Message-ID: <1bc4fe22-61ee-182e-733b-5e572491eeae@redhat.com> (raw)
In-Reply-To: <20220316114527.894808-1-ktraynor@redhat.com>

On 16/03/2022 11:45, Kevin Traynor wrote:
> Suppress of rte_crypto_asym_op was added in dpdk main branch
> as part of
> a678c5d36589 ("cryptodev: add DSA random number k")
> 
> That is not backported to 21.11 branch, but other commit
> f092922c3674 ("cryptodev: fix RSA key type name")
> also needs this suppression.
> 
> Add the suppression here.
> 
> Fixes: f092922c3674 ("cryptodev: fix RSA key type name")
> Cc: arkadiuszx.kusztal@intel.com
> 
> Reported-by: https://lab.dpdk.org/results/dashboard/tarballs/19132
> Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---

Will apply this by EOD if no objections so the nightly CI will pass.

>   devtools/libabigail.abignore | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/devtools/libabigail.abignore b/devtools/libabigail.abignore
> index 004fd53180..146a601ed3 100644
> --- a/devtools/libabigail.abignore
> +++ b/devtools/libabigail.abignore
> @@ -13,4 +13,8 @@
>           name_regexp = _pmd_info$
>   
> +; Ignore changes to rte_crypto_asym_op, asymmetric crypto API is experimental
> +[suppress_type]
> +        name = rte_crypto_asym_op
> +
>   ; Ignore section attribute fixes in experimental regexdev library
>   [suppress_file]


  reply	other threads:[~2022-03-16 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 11:45 Kevin Traynor
2022-03-16 16:08 ` Kevin Traynor [this message]
2022-03-16 16:14 ` David Marchand
2022-03-16 16:51   ` Kevin Traynor

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=1bc4fe22-61ee-182e-733b-5e572491eeae@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=stable@dpdk.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).