From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 4/5] [gdb] Fix syscalls-info -> syscalls_info in syscalls/gdb-syscalls.dtd
Date: Wed, 26 Aug 2026 23:22:08 +0200 [thread overview]
Message-ID: <20260826212209.925066-5-tdevries@suse.de> (raw)
In-Reply-To: <20260826212209.925066-1-tdevries@suse.de>
When running xmllint with --valid, we get:
...
gdb/syscalls/ppc64-linux.xml:433: element syscalls_info: validity error : \
No declaration for element syscalls_info
</syscalls_info>
^
...
Fix this by changing syscalls-info to syscalls_info in syscalls/gdb-syscalls.dtd.
---
gdb/syscalls/gdb-syscalls.dtd | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/syscalls/gdb-syscalls.dtd b/gdb/syscalls/gdb-syscalls.dtd
index 09dff02910f..35a676fa585 100644
--- a/gdb/syscalls/gdb-syscalls.dtd
+++ b/gdb/syscalls/gdb-syscalls.dtd
@@ -4,9 +4,9 @@
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. -->
-<!-- The root element of a syscall info is <syscalls-info>. -->
+<!-- The root element of a syscall info is <syscalls_info>. -->
-<!ELEMENT syscalls-info (syscall*)>
+<!ELEMENT syscalls_info (syscall*)>
<!ELEMENT syscall EMPTY>
<!ATTLIST syscall
--
2.51.0
next prev parent reply other threads:[~2026-08-26 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 21:22 [PATCH v2 0/5] [gdb] xml linting Tom de Vries
2026-08-26 21:22 ` [PATCH v2 1/5] [pre-commit] Check xml files Tom de Vries
2026-08-26 21:22 ` [PATCH v2 2/5] [gdb] Fix xmllint namespace errors Tom de Vries
2026-08-26 21:22 ` [PATCH v2 3/5] [gdb] Fix target element validity error in features/gdb-target.dtd Tom de Vries
2026-08-26 21:22 ` Tom de Vries [this message]
2026-08-26 21:22 ` [PATCH v2 5/5] [pre-commit] Use --valid with xmllint 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=20260826212209.925066-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