From: Dodji Seketeli <dodji@redhat.com>
To: libabigail@sourceware.org
Subject: [PATCH, applied to master] PR25409-librte_bus_dpaa.so.20.0.abi: Update to 2.3
Date: Sun, 18 Feb 2024 13:08:16 +0100 [thread overview]
Message-ID: <87zfvyug9b.fsf@redhat.com> (raw)
Hello,
The PR25409-librte_bus_dpaa.so.20.0.abi test input file was modified
at least because of the patch to fix zero-length arrays IR for
https://sourceware.org/bugzilla/show_bug.cgi?id=31377.
That modification came after the introduction of the pointer-to-member
type feature, which bumped the ABIXML version to 2.3. So,
PR25409-librte_bus_dpaa.so.20.0.abi should see its ABIXML version
change to 2.3 too. This patch makes that adjustment.
The reason why the patch to fix zero-length arrays IR hasn't bumped
the ABIXML version to 2.3 has to do with easing the potential
back-porting into the libabigail-2.4-branch.
* tests/data/test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi:
Bump ABIXML version to 2.3.
Signed-off-by: Dodji Seketeli <dodji@redhat.com>
Applied to the master branch.
---
.../test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/data/test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi b/tests/data/test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi
index b600a18d..eeaf6e26 100644
--- a/tests/data/test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi
+++ b/tests/data/test-diff-dwarf-abixml/PR25409-librte_bus_dpaa.so.20.0.abi
@@ -1,4 +1,4 @@
-<abi-corpus version='2.2' soname='librte_bus_dpaa.so.20.0'>
+<abi-corpus version='2.3' soname='librte_bus_dpaa.so.20.0'>
<elf-needed>
<dependency name='libm.so.6'/>
<dependency name='libdl.so.2'/>
--
2.39.3
--
Dodji
reply other threads:[~2024-02-18 12:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zfvyug9b.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=libabigail@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).