From: Eli Zaretskii <eliz@gnu.org>
To: Luis <luis.machado.foss@gmail.com>
Cc: Ezra.Sitorus@arm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 6/6] gdb/doc: Document AArch64 FPMR support
Date: Mon, 10 Nov 2025 14:00:03 +0200 [thread overview]
Message-ID: <86fram3xoc.fsf@gnu.org> (raw)
In-Reply-To: <a2df8abd-de0f-4482-aa29-4313334044a4@gmail.com> (message from Luis on Sun, 9 Nov 2025 20:15:04 +0000)
> Date: Sun, 9 Nov 2025 20:15:04 +0000
> From: Luis <luis.machado.foss@gmail.com>
>
> 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.
I hope I'm not confused: according to my records, I've reviewed this
series on Oct 31 and posted my review then, see
https://sourceware.org/pipermail/gdb-patches/2025-October/222254.html
next prev parent reply other threads:[~2025-11-10 12:01 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 [this message]
2025-11-10 17:28 ` Ezra Sitorus
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=86fram3xoc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Ezra.Sitorus@arm.com \
--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