From: Palmer Dabbelt <palmer@rivosinc.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: The RISC-V vector registers didn't change
Date: Thu, 23 Feb 2023 13:52:16 -0800 (PST) [thread overview]
Message-ID: <mhng-9a36b01b-bc18-4435-9e62-443fbde92034@palmer-ri-x1c9a> (raw)
In-Reply-To: <83h6wccuje.fsf@gnu.org>
On Thu, 26 Jan 2023 23:21:09 PST (-0800), eliz@gnu.org wrote:
>> Date: Thu, 26 Jan 2023 15:12:00 -0800
>> Cc: Palmer Dabbelt <palmer@rivosinc.com>
>> From: Palmer Dabbelt <palmer@rivosinc.com>
>>
>> When we merged the GDB vector register support we did it a bit early,
>> just eating the risk in the very unlikely case that the vector register
>> names changed. They didn't, so we can now remove the caveat in the docs
>> that they might.
>> ---
>> gdb/doc/gdb.texinfo | 6 +-----
>> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> This is OK, thanks.
Committed, thanks!
prev parent reply other threads:[~2023-02-23 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 23:12 Palmer Dabbelt
2023-01-27 7:21 ` Eli Zaretskii
2023-02-23 21:52 ` Palmer Dabbelt [this message]
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=mhng-9a36b01b-bc18-4435-9e62-443fbde92034@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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).