From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org, thiago.bauermann@linaro.org
Subject: Re: [PATCH v3 6/6] [gdb/docs] sme2: Document SME2 registers and features
Date: Thu, 07 Sep 2023 18:46:53 +0300 [thread overview]
Message-ID: <83zg1yx9xu.fsf@gnu.org> (raw)
In-Reply-To: <20230907152049.1031425-7-luis.machado@arm.com> (message from Luis Machado via Gdb-patches on Thu, 7 Sep 2023 16:20:49 +0100)
> CC: <thiago.bauermann@linaro.org>
> Date: Thu, 7 Sep 2023 16:20:49 +0100
> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
>
> v3:
>
> - Fixed formatting.
> - Fixed period after xfer.
>
> --
>
> Document changes introduced by gdb's SME2 support.
> ---
> gdb/NEWS | 3 +++
> gdb/doc/gdb.texinfo | 65 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 68 insertions(+)
Thanks, this is okay.
Approved-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-09-07 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 15:20 [PATCH v3 0/6] SME2 support for AArch64 gdb/gdbserver on Linux Luis Machado
2023-09-07 15:20 ` [PATCH v3 1/6] [gdb/aarch64] sme2: Enable SME2 for AArch64 gdb " Luis Machado
2023-09-07 15:20 ` [PATCH v3 2/6] [gdbserver/aarch64] sme2: Enable SME2 support in gdbserver Luis Machado
2023-09-07 15:20 ` [PATCH v3 3/6] [gdb/aarch64] sme2: signal frame support Luis Machado
2023-09-07 15:20 ` [PATCH v3 4/6] [gdb/aarch64] sme2: Core file support for ZT register set Luis Machado
2023-09-07 15:20 ` [PATCH v3 5/6] [gdb/testsuite] sme2: Extend SME tests to include SME2 Luis Machado
2023-09-07 15:20 ` [PATCH v3 6/6] [gdb/docs] sme2: Document SME2 registers and features Luis Machado
2023-09-07 15:46 ` Eli Zaretskii [this message]
2023-09-13 3:28 ` [PATCH v3 0/6] SME2 support for AArch64 gdb/gdbserver on Linux Thiago Jung Bauermann
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=83zg1yx9xu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).