From: Ezra Sitorus <ezra.sitorus@arm.com>
To: Luis <luis.machado.foss@gmail.com>
Cc: <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v4 6/6] gdb/doc: Document AArch64 FPMR support
Date: Mon, 10 Nov 2025 17:28:01 +0000 [thread overview]
Message-ID: <aRIgoeAd-0IdlUze@D2G2X7XGD1> (raw)
In-Reply-To: <a2df8abd-de0f-4482-aa29-4313334044a4@gmail.com>
Hi all,
On Sun, Nov 09, 2025 at 08:15:04PM +0000, Luis wrote:
> I have no further comments on this one. Once Eli is happy with the
> documentation changes, please push the series. If you don�t have commit
> access yet, I can do that for you.
>
Just to double check, are we treating commit access to binutils the same as
for gdb? If they're different then I only have access to binutils.
Am I right in thinking also that each patch requires an 'Approved-By' (and
'Reviewed-By' as well for the news/doc patch) line at the end of the commit
message? What happens if this isn't added?
Ezra
next prev parent reply other threads:[~2025-11-10 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:16 [PATCH v4 0/6] gdb/aarch64: Support for FPMR Ezra.Sitorus
2025-10-31 15:16 ` [PATCH v4 1/6] gdb/aarch64: Enable FPMR for AArch64 in gdb on Linux Ezra.Sitorus
2025-10-31 15:16 ` [PATCH v4 2/6] gdbserver/aarch64: Enable FPMR for AArch64 in gdbserver " Ezra.Sitorus
2025-10-31 15:16 ` [PATCH v4 3/6] gdb/aarch64: signal frame support for fpmr Ezra.Sitorus
2025-10-31 15:16 ` [PATCH v4 4/6] gdb/aarch64: core file support for FPMR Ezra.Sitorus
2025-10-31 15:16 ` [PATCH v4 5/6] gdb/aarch64: Tests for fpmr Ezra.Sitorus
2025-11-09 20:11 ` Luis
2025-10-31 15:16 ` [PATCH v4 6/6] gdb/doc: Document AArch64 FPMR support Ezra.Sitorus
2025-10-31 16:57 ` Eli Zaretskii
2025-11-09 20:15 ` Luis
2025-11-10 12:00 ` Eli Zaretskii
2025-11-10 17:28 ` Ezra Sitorus [this message]
2025-11-14 7:38 ` 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=aRIgoeAd-0IdlUze@D2G2X7XGD1 \
--to=ezra.sitorus@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@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