From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Cc: Nicholas Vinson <nvinson234@gmail.com>
Subject: Re: [PATCH libctf 00/22] more modifiable CTF dicts (and a few bugfixes)
Date: Fri, 19 Apr 2024 16:51:19 +0100 [thread overview]
Message-ID: <87le59s64o.fsf@esperi.org.uk> (raw)
In-Reply-To: <20240417202018.34966-1-nick.alcock@oracle.com> (Nick Alcock's message of "Wed, 17 Apr 2024 21:19:56 +0100")
On 17 Apr 2024, Nick Alcock stated:
> I'll apply it in a couple of days if nobody says otherwise.
>
> Cc: Nicholas Vinson <nvinson234@gmail.com>
>
> Nicholas Vinson (1):
> libctf: Remove undefined functions from ver. map
>
> Nick Alcock (21):
> binutils, objdump: Add --ctf-parent-section
> libctf: don't leak the symbol name in the name->type cache
> libctf: remove static/dynamic name lookup distinction
> libctf: fix name lookup in dicts containing base-type bitfields
> libctf: support addition of types to dicts read via ctf_open()
> libctf: fix a comment
> libctf: delete LCTF_DIRTY
> libctf: fix a comment typo
> libctf: rename ctf_dict.ctf_{symtab,strtab}
> Revert "libctf: do not corrupt strings across ctf_serialize"
> libctf: replace 'pending refs' abstraction
> libctf: rethink strtab writeout
> libctf: make ctf_serialize() actually serialize
> libctf: fix tiny dumping error
> libctf: improve handling of type dumping errors
> libctf: make ctf_lookup of symbols by name work in more cases
> libctf: fix a debugging typo
> libctf: add rewriting tests
> libctf: fix leak in test
> libctf: don't pass errno into ctf_err_warn so often
> libctf: do not include undefined functions in libctf.ver
This is pushed now, exactly as here except for a couple of tiny GNU
style fixes (the one pointed out by Alan, and a few similar ones in a
couple of other commits).
prev parent reply other threads:[~2024-04-19 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 20:19 Nick Alcock
2024-04-17 20:19 ` [PATCH 01/22] binutils, objdump: Add --ctf-parent-section Nick Alcock
2024-04-18 2:05 ` Alan Modra
2024-04-18 13:06 ` Nick Alcock
2024-04-17 20:19 ` [PATCH 02/22] libctf: don't leak the symbol name in the name->type cache Nick Alcock
2024-04-17 20:19 ` [PATCH 03/22] libctf: remove static/dynamic name lookup distinction Nick Alcock
2024-04-17 20:20 ` [PATCH 04/22] libctf: fix name lookup in dicts containing base-type bitfields Nick Alcock
2024-04-17 20:20 ` [PATCH 05/22] libctf: support addition of types to dicts read via ctf_open() Nick Alcock
2024-04-17 20:20 ` [PATCH 06/22] libctf: fix a comment Nick Alcock
2024-04-17 20:20 ` [PATCH 07/22] libctf: delete LCTF_DIRTY Nick Alcock
2024-04-17 20:20 ` [PATCH 08/22] libctf: fix a comment typo Nick Alcock
2024-04-17 20:20 ` [PATCH 09/22] libctf: rename ctf_dict.ctf_{symtab,strtab} Nick Alcock
2024-04-17 20:20 ` [PATCH 10/22] Revert "libctf: do not corrupt strings across ctf_serialize" Nick Alcock
2024-04-17 20:20 ` [PATCH 11/22] libctf: replace 'pending refs' abstraction Nick Alcock
2024-04-17 20:20 ` [PATCH 12/22] libctf: rethink strtab writeout Nick Alcock
2024-04-17 20:20 ` [PATCH 13/22] libctf: make ctf_serialize() actually serialize Nick Alcock
2024-04-17 20:20 ` [PATCH 14/22] libctf: fix tiny dumping error Nick Alcock
2024-04-17 20:20 ` [PATCH 15/22] libctf: improve handling of type dumping errors Nick Alcock
2024-04-17 20:20 ` [PATCH 16/22] libctf: make ctf_lookup of symbols by name work in more cases Nick Alcock
2024-04-17 20:20 ` [PATCH 17/22] libctf: fix a debugging typo Nick Alcock
2024-04-17 20:20 ` [PATCH 18/22] libctf: add rewriting tests Nick Alcock
2024-04-17 20:20 ` [PATCH 19/22] libctf: fix leak in test Nick Alcock
2024-04-17 20:20 ` [PATCH 20/22] libctf: don't pass errno into ctf_err_warn so often Nick Alcock
2024-04-17 20:20 ` [PATCH 21/22] libctf: Remove undefined functions from ver. map Nick Alcock
2024-04-17 20:20 ` [PATCH 22/22] libctf: do not include undefined functions in libctf.ver Nick Alcock
2024-04-19 15:51 ` Nick Alcock [this message]
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=87le59s64o.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=nvinson234@gmail.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).