From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Subject: [PATCH v2 0/2] ABI check updates
Date: Thu, 23 Mar 2023 18:15:00 +0100 [thread overview]
Message-ID: <20230323171502.3124049-1-david.marchand@redhat.com> (raw)
In-Reply-To: <20221103154717.22368-1-david.marchand@redhat.com>
This series moves ABI exceptions in a single configuration file and
simplifies the ABI check so that no artefact depending on libabigail
version is stored in the CI.
--
David Marchand
Changes since v1:
- rebased after abi check parallelisation rework,
David Marchand (2):
devtools: unify configuration for ABI check
devtools: stop depending on libabigail xml format
.ci/linux-build.sh | 4 ----
.github/workflows/build.yml | 2 +-
MAINTAINERS | 1 -
devtools/check-abi.sh | 24 +++++++++++++++---------
devtools/gen-abi.sh | 27 ---------------------------
devtools/libabigail.abignore | 12 +++++++++---
devtools/test-meson-builds.sh | 5 -----
7 files changed, 25 insertions(+), 50 deletions(-)
delete mode 100755 devtools/gen-abi.sh
--
2.39.2
next prev parent reply other threads:[~2023-03-23 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:47 [PATCH " David Marchand
2022-11-03 15:47 ` [PATCH 1/2] devtools: unify configuration for ABI check David Marchand
2022-11-03 15:47 ` [PATCH 2/2] devtools: stop depending on libabigail xml format David Marchand
2023-03-23 17:15 ` David Marchand [this message]
2023-03-23 17:15 ` [PATCH v2 1/2] devtools: unify configuration for ABI check David Marchand
2023-03-23 17:15 ` [PATCH v2 2/2] devtools: stop depending on libabigail xml format David Marchand
2023-03-28 18:38 ` [PATCH v2 0/2] ABI check updates 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=20230323171502.3124049-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@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).