Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 4/7] [pre-commit] Make gdb/nat codespell-clean
Date: Tue, 10 Mar 2026 10:18:40 +0100	[thread overview]
Message-ID: <20260310091843.3214063-5-tdevries@suse.de> (raw)
In-Reply-To: <20260310091843.3214063-1-tdevries@suse.de>

Fix typos in gdb/nat, and add "fpr" to gdb/contrib/codespell-ignore-words.txt.
---
 .pre-commit-config.yaml                | 2 +-
 gdb/contrib/codespell-ignore-words.txt | 1 +
 gdb/nat/linux-btrace.c                 | 2 +-
 3 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index c0aea1488be..bb6bc2b4e54 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -71,7 +71,7 @@ repos:
     rev: v2.4.2
     hooks:
     - id: codespell
-      files: '^(gdbsupport|gdbserver|gdb/(contrib|dwarf2|tui|target|data-directory|po|system-gdbinit|mi|syscalls|arch|regformats|compile|python|guile|config|unittests|cli|testsuite/gdb.(ctf|dap|debuginfod|gdb|go|guile|mi|modula2|objc|opencl|opt|pascal|perf|replay|reverse|rocm|server|stabs|testsuite|tui|xml)))/'
+      files: '^(gdbsupport|gdbserver|gdb/(nat|contrib|dwarf2|tui|target|data-directory|po|system-gdbinit|mi|syscalls|arch|regformats|compile|python|guile|config|unittests|cli|testsuite/gdb.(ctf|dap|debuginfod|gdb|go|guile|mi|modula2|objc|opencl|opt|pascal|perf|replay|reverse|rocm|server|stabs|testsuite|tui|xml)))/'
       args: [--toml, gdb/pyproject.toml]
     - id: codespell
       name: codespell-log
diff --git a/gdb/contrib/codespell-ignore-words.txt b/gdb/contrib/codespell-ignore-words.txt
index c07df0c001d..c86bd3f0972 100644
--- a/gdb/contrib/codespell-ignore-words.txt
+++ b/gdb/contrib/codespell-ignore-words.txt
@@ -2,3 +2,4 @@ configury
 SME
 Synopsys
 aranges
+fpr
diff --git a/gdb/nat/linux-btrace.c b/gdb/nat/linux-btrace.c
index 46aa2b730a7..1bd3ccb8d31 100644
--- a/gdb/nat/linux-btrace.c
+++ b/gdb/nat/linux-btrace.c
@@ -99,7 +99,7 @@ btrace_this_cpu (void)
   return cpu;
 }
 
-/* Return non-zero if there is new data in PEVENT; zero otherwise.  */
+/* Return non-zero if there is new data in PEV; zero otherwise.  */
 
 static int
 perf_event_new_data (const struct perf_event_buffer *pev)
-- 
2.51.0


  parent reply	other threads:[~2026-03-10  9:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  9:18 [PATCH 0/7] [pre-commit] Some codespell fixes Tom de Vries
2026-03-10  9:18 ` [PATCH 1/7] [pre-commit] Make codespell:ignore-begin/end non-greedy Tom de Vries
2026-03-10  9:18 ` [PATCH 2/7] [pre-commit] Move gdb/contrib/setup.cfg to gdb/pyproject.toml Tom de Vries
2026-03-10  9:18 ` [PATCH 3/7] [pre-commit] Make gdb/contrib codespell-clean Tom de Vries
2026-03-10  9:18 ` Tom de Vries [this message]
2026-03-10  9:18 ` [PATCH 5/7] [pre-commit] Make gdb/features codespell-clean Tom de Vries
2026-03-10  9:18 ` [PATCH 6/7] [pre-commit] Make gdb/stubs codespell-clean Tom de Vries
2026-03-10  9:18 ` [PATCH 7/7] [pre-commit] Make gdb/doc codespell-clean Tom de Vries
2026-03-24 15:37 ` [PING][PATCH 0/7] [pre-commit] Some codespell fixes Tom de Vries
2026-04-10 12:38 ` Tom de Vries
2026-04-24 13:20   ` [PING^2][PATCH " Tom de Vries
2026-06-01 12:34     ` Tom de Vries

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=20260310091843.3214063-5-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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