From: "dodji at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30931] New: Support check-uapi.sh
Date: Mon, 02 Oct 2023 13:53:06 +0000 [thread overview]
Message-ID: <bug-30931-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30931
Bug ID: 30931
Summary: Support check-uapi.sh
Product: libabigail
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: dodji at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
A new script used to check the compatibility of changes the user ABI hearders
of the Linux kernel is in the process of being upstreamed. The script uses
libabigail and thus needs some improvements in the code base of the project.
This enhancement request is to track those improvements.
The post kicking off this effort is at
https://inbox.sourceware.org/libabigail/5363161d-8167-284e-e35d-9a8ef20adea9@quicinc.com/.
The improvement needed on the libabigail from are expressed here:
https://inbox.sourceware.org/libabigail/340b33bd-2b43-9f99-58e1-f1b77a51b48a@quicinc.com/.
The branch where patches for this effort are going to be accumulated until
their merging into the mainline branch is at
https://sourceware.org/git/?p=libabigail.git;a=shortlog;h=refs/heads/users/dodji/check-uapi-support.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-10-02 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 13:53 dodji at redhat dot com [this message]
2023-10-02 13:57 ` [Bug default/30931] " dodji at redhat dot com
2023-10-05 13:31 ` dodji at redhat dot com
2023-10-12 15:48 ` dodji at redhat dot com
2023-10-13 15:27 ` dodji at redhat dot com
2023-10-13 17:13 ` quic_johmoo at quicinc dot com
2023-10-13 19:32 ` dodji at redhat dot com
2023-10-17 8:59 ` dodji at redhat dot com
2023-10-20 23:08 ` dodji at redhat dot com
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=bug-30931-9487@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).