DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Shijith Thotton <sthotton@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [EXT] Re:  [pull-request] next-crypto 21.08 rc1
Date: Thu, 8 Jul 2021 07:39:25 +0000	[thread overview]
Message-ID: <CO6PR18MB448469EE8BDFE6561A104911D8199@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <2086219.nnIR5hDg31@thomas>

> 07/07/2021 21:30, Akhil Goyal:
> > Shijith Thotton (2):
> >       drivers: add octeontx crypto adapter framework
> >       drivers: add octeontx crypto adapter data path
> 
> It seems there is an ABI breakage:
> 
> devtools/check-abi.sh: line 38: 958581 Segmentation fault
> (core dumped) abidiff $ABIDIFF_OPTIONS $dump $dump2
> Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --
> no-added-syms --headers-dir1 v21.05/build-gcc-shared/usr/local/include --
> headers-dir2 build-gcc-shared/install/usr/local/include v21.05/build-gcc-
> shared/dump/librte_crypto_octeontx.dump build-gcc-
> shared/install/dump/librte_crypto_octeontx.dump'
> 
> Without this series, the ABI check is passing.
> 

I do not see this error at my end + there is no such issue reported on CI.
On CI it failed only on FreeBSD, and that too was a false report.

Can you paste the output of
'abidiff --suppr devtools/libabigail.abignore --no-added-syms --headers-dir1 v21.05/build-gcc-shared/usr/local/include --headers-dir2 build-gcc-shared/install/usr/local/include v21.05/build-gcc-shared/dump/librte_crypto_octeontx.dump build-gcc-shared/install/dump/librte_crypto_octeontx.dump'

Regards,
Akhil

  reply	other threads:[~2021-07-08  7:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 19:30 [dpdk-dev] " Akhil Goyal
2021-07-07 21:57 ` Thomas Monjalon
2021-07-08  7:39   ` Akhil Goyal [this message]
2021-07-08  7:41   ` Thomas Monjalon
2021-07-08  7:47     ` David Marchand
2021-07-08  7:48     ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-08 17:13 ` [dpdk-dev] " Ali Alnubani
2021-07-08 20:16   ` David Marchand
2021-07-09  4:24     ` [dpdk-dev] [EXT] " Anoob Joseph
2021-07-09  6:43       ` David Marchand
2021-07-09  9:00         ` Anoob Joseph

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=CO6PR18MB448469EE8BDFE6561A104911D8199@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=sthotton@marvell.com \
    --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).