From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: Nick Clifton <nickc@redhat.com>
Cc: Nick Alcock <nick.alcock@oracle.com>, binutils@sourceware.org
Subject: Re: [PATCH v2 00/19] libctf, and CTF support for objdump and readelf
Date: Tue, 28 May 2019 16:39:00 -0000 [thread overview]
Message-ID: <878suqh6u0.fsf@oracle.com> (raw)
In-Reply-To: <4946341d-9309-7f8b-bbfb-f1e08153e921@redhat.com> (Nick Clifton's message of "Tue, 28 May 2019 09:33:41 +0100")
> Nick Alcock (19):
> include: new header ctf.h: file format description
> include: new header ctf-api.h
> libctf: lowest-level memory allocation and debug-dumping wrappers
> libctf: low-level list manipulation and helper utilities
> libctf: error handling
> libctf: hashing
> libctf: implementation definitions related to file creation
> libctf: creation functions
> libctf: opening
> libctf: ELF file opening via BFD
> libctf: core type lookup
> libctf: lookups by name and symbol
> libctf: type copying
> libctf: library version enforcement
> libctf: mmappable archives
> libctf: labels
> libctf: debug dumping
> libctf: build system
> binutils: CTF support for objdump and readelf
Patch series approved (all of it) - please apply.
Just pushed it in behalf of Nix, with the additions you suggested.
Thanks!
next prev parent reply other threads:[~2019-05-28 16:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 22:10 Nick Alcock
2019-05-17 22:10 ` [PATCH v2 14/19] libctf: library version enforcement Nick Alcock
2019-05-17 22:10 ` [PATCH v2 08/19] libctf: creation functions Nick Alcock
2019-05-29 14:09 ` Szabolcs Nagy
2019-05-29 14:19 ` Nick Alcock
2019-05-17 22:10 ` [PATCH v2 04/19] libctf: low-level list manipulation and helper utilities Nick Alcock
2019-05-17 22:10 ` [PATCH v2 13/19] libctf: type copying Nick Alcock
2019-05-17 22:10 ` [PATCH v2 09/19] libctf: opening Nick Alcock
2019-05-17 22:10 ` [PATCH v2 10/19] libctf: ELF file opening via BFD Nick Alcock
2019-05-17 22:10 ` [PATCH v2 02/19] include: new header ctf-api.h Nick Alcock
2019-05-17 22:10 ` [PATCH v2 12/19] libctf: lookups by name and symbol Nick Alcock
2019-05-17 22:10 ` [PATCH v2 05/19] libctf: error handling Nick Alcock
2019-05-17 22:10 ` [PATCH v2 17/19] libctf: debug dumping Nick Alcock
2019-05-17 22:10 ` [PATCH v2 01/19] include: new header ctf.h: file format description Nick Alcock
2019-05-17 22:10 ` [PATCH v2 07/19] libctf: implementation definitions related to file creation Nick Alcock
2019-05-17 22:10 ` [PATCH v2 03/19] libctf: lowest-level memory allocation and debug-dumping wrappers Nick Alcock
2019-05-17 22:10 ` [PATCH v2 06/19] libctf: hashing Nick Alcock
2019-05-17 22:10 ` [PATCH v2 19/19] binutils: CTF support for objdump and readelf Nick Alcock
2019-05-17 22:10 ` [PATCH v2 15/19] libctf: mmappable archives Nick Alcock
2019-05-17 22:11 ` [PATCH v2 18/19] libctf: build system Nick Alcock
2019-05-17 22:12 ` [PATCH v2 11/19] libctf: core type lookup Nick Alcock
2019-05-17 22:12 ` [PATCH v2 16/19] libctf: labels Nick Alcock
2019-05-20 19:27 ` [PATCH v2 00/19] libctf, and CTF support for objdump and readelf Joseph Myers
2019-05-20 20:50 ` Nick Alcock
2019-05-28 8:33 ` Nick Clifton
2019-05-28 9:56 ` Nick Alcock
2019-05-28 16:39 ` Jose E. Marchesi [this message]
2019-05-28 19:16 ` Christophe Lyon
2019-05-28 21:36 ` Nix
2019-05-29 3:25 ` Alan Modra
2019-05-29 9:14 ` Jose E. Marchesi
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=878suqh6u0.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=binutils@sourceware.org \
--cc=nick.alcock@oracle.com \
--cc=nickc@redhat.com \
/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).