From: Tom de Vries <tdevries@suse.de>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Matthieu Longo <matthieu.longo@arm.com>
Cc: gdb-patches@sourceware.org, Alan Hayward <alan.hayward@arm.com>,
Luis Machado <luis.machado.foss@gmail.com>
Subject: Re: [PATCH v1] gdb/aarch64: fix typo gcs_availabe
Date: Mon, 8 Jun 2026 15:52:35 +0200 [thread overview]
Message-ID: <e8ff449d-693a-4e06-a2f0-41db625518f8@suse.de> (raw)
In-Reply-To: <87fr2zw0a5.fsf@linaro.org>
On 6/7/26 4:29 AM, Thiago Jung Bauermann wrote:
> Matthieu Longo <matthieu.longo@arm.com> writes:
>
>> ---
>> gdb/aarch64-linux-tdep.c | 6 +++---
>> gdb/arch/aarch64.h | 1 +
>> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> Thank you! This is ok.
>
FWIW, I got curious about whether codespell would detect this typo, and
posted my findings in a PR (
https://sourceware.org/bugzilla/show_bug.cgi?id=34241 ).
Thanks,
- Tom
> Approved-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
>
> This doesn't even need an approval, actually. It falls under the obvious
> fix rule mentioned in gdb/MAINTAINERS.
>
prev parent reply other threads:[~2026-06-08 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 16:48 Matthieu Longo
2026-06-07 2:29 ` Thiago Jung Bauermann
2026-06-08 13:52 ` Tom de Vries [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=e8ff449d-693a-4e06-a2f0-41db625518f8@suse.de \
--to=tdevries@suse.de \
--cc=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado.foss@gmail.com \
--cc=matthieu.longo@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