From: Michael Eager <eager@eagerm.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [pushed] [gdb] Fix typo in gdb/microblaze-linux-nat.c
Date: Mon, 15 Jun 2026 18:26:34 -0700 [thread overview]
Message-ID: <ea9d54e3-d854-43bc-8db3-587b2868f3de@eagerm.com> (raw)
In-Reply-To: <20260615112925.3587003-1-tdevries@suse.de>
Thanks.
On 6/15/26 4:29 AM, Tom de Vries wrote:
> Result of:
> ...
> $ codespell --toml gdb/pyproject.toml -w -i3 gdb/microblaze-linux-nat.c
> /* Transfering floating-point registers between GDB, inferiors and cores.
> Transfering ==> Transferring (Y/n)
> FIXED: gdb/microblaze-linux-nat.c
> gdb/microblaze-linux-nat.c:97: Transfering ==> Transferring
> ...
> ---
> gdb/microblaze-linux-nat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/microblaze-linux-nat.c b/gdb/microblaze-linux-nat.c
> index 1da0c04366d..d2d34071f3f 100644
> --- a/gdb/microblaze-linux-nat.c
> +++ b/gdb/microblaze-linux-nat.c
> @@ -94,7 +94,7 @@ fill_gregset (const struct regcache *regcache, prgregset_t *gregs, int regnum)
> regcache->raw_collect (regnum, regp + regnum);
> }
>
> -/* Transfering floating-point registers between GDB, inferiors and cores.
> +/* Transferring floating-point registers between GDB, inferiors and cores.
> Since MicroBlaze floating-point registers are the same as GPRs these do
> nothing. */
>
>
> base-commit: 0c73540bb80ffb5c88da71e3162b7a01e5b9db61
prev parent reply other threads:[~2026-06-16 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 11:29 Tom de Vries
2026-06-16 1:26 ` Michael Eager [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=ea9d54e3-d854-43bc-8db3-587b2868f3de@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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