From: Eli Zaretskii <eliz@gnu.org>
To: Ezra Sitorus <ezra.sitorus@arm.com>
Cc: gdb-patches@sourceware.org, luis.machado.foss@gmail.com,
thiago.bauermann@linaro.org
Subject: Re: [PATCH v3 6/6] gdb/doc: Document AArch64 FPMR support
Date: Wed, 22 Oct 2025 14:53:46 +0300 [thread overview]
Message-ID: <86tszrup85.fsf@gnu.org> (raw)
In-Reply-To: <aPii_WJ5IddrDSL1@D2G2X7XGD1> (message from Ezra Sitorus on Wed, 22 Oct 2025 10:25:17 +0100)
> Date: Wed, 22 Oct 2025 10:25:17 +0100
> From: Ezra Sitorus <ezra.sitorus@arm.com>
> CC: <gdb-patches@sourceware.org>, <luis.machado.foss@gmail.com>,
> <thiago.bauermann@linaro.org>
>
> > > +@subsubsection AArch64 Floating Point Mode Register
> > > +@cindex Floating Point Mode Register, AArch64
> > > +@cindex FPMR, AArch64
> >
> > Index entries should preferably not us upper-case letters, so that
> > their sorting does not depend on locale-specific rules. So please use
> > upper-case letters only in acronyms.
> >
>
> I don't mind changing it to lowercase, but the other AArch64 entries use upper case
> as well, e.g.
>
> @subsubsection AArch64 Memory Tagging Extension
> @cindex Memory Tagging Extension, AArch64
> @cindex MTE, AArch64
They should all be down-cased, but there's no need to do that as part
of this patch. Also, "Memory Tagging Extension" is a kind-of proper
name, whereas "Floating Point Mode Register" isn't.
In any case, there's no reason to proliferate a mistake even if we
have some already.
Thanks.
next prev parent reply other threads:[~2025-10-22 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:02 [PATCH v3 0/6] gdb/aarch64: Support for FPMR Ezra.Sitorus
2025-10-21 15:02 ` [PATCH v3 1/6] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-10-27 22:32 ` Luis
2025-10-21 15:02 ` [PATCH v3 2/6] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-10-27 22:26 ` Luis
2025-10-21 15:02 ` [PATCH v3 3/6] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-10-27 22:25 ` Luis
2025-10-21 15:02 ` [PATCH v3 4/6] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-10-27 22:23 ` Luis
2025-10-21 15:02 ` [PATCH v3 5/6] gdb/aarch64: Tests " Ezra.Sitorus
2025-10-27 22:19 ` Luis
2025-10-21 15:03 ` [PATCH v3 6/6] gdb/doc: Document AArch64 FPMR support Ezra.Sitorus
2025-10-21 15:35 ` Eli Zaretskii
2025-10-22 9:25 ` Ezra Sitorus
2025-10-22 11:53 ` Eli Zaretskii [this message]
2025-10-27 22:08 ` Luis
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=86tszrup85.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ezra.sitorus@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=thiago.bauermann@linaro.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