From: Nick Alcock <nix@sourceware.org>
To: binutils-cvs@sourceware.org
Subject: [binutils-gdb] libctf: fix a comment typo
Date: Fri, 19 Apr 2024 15:51:34 +0000 (GMT) [thread overview]
Message-ID: <20240419155134.7BE0F3849AE9@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bb2a9a465e02e8cee00736351d10bde914f50758
commit bb2a9a465e02e8cee00736351d10bde914f50758
Author: Nick Alcock <nick.alcock@oracle.com>
Date: Fri Jan 5 11:12:37 2024 +0000
libctf: fix a comment typo
ctf_update has been called ctf_serialize for years now.
libctf/
* ctf-impl.h: Fix comment typo.
Diff:
---
libctf/ctf-impl.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libctf/ctf-impl.h b/libctf/ctf-impl.h
index dc57d6f64c7..b7123317c98 100644
--- a/libctf/ctf-impl.h
+++ b/libctf/ctf-impl.h
@@ -199,13 +199,13 @@ typedef struct ctf_err_warning
} ctf_err_warning_t;
/* Atoms associate strings with a list of the CTF items that reference that
- string, so that ctf_update() can instantiate all the strings using the
+ string, so that ctf_serialize() can instantiate all the strings using the
ctf_str_atoms and then reassociate them with the real string later.
Strings can be interned into ctf_str_atom without having refs associated
with them, for values that are returned to callers, etc. Items are only
- removed from this table on ctf_close(), but on every ctf_update(), all the
- csa_refs in all entries are purged. */
+ removed from this table on ctf_close(), but on every ctf_serialize(), all
+ the csa_refs in all entries are purged. */
typedef struct ctf_str_atom
{
next reply other threads:[~2024-04-19 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 15:51 Nick Alcock [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-24 14:08 Nick Alcock
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=20240419155134.7BE0F3849AE9@sourceware.org \
--to=nix@sourceware.org \
--cc=binutils-cvs@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).