From: Markus Armbruster <armbru@redhat.com>
To: dave@treblig.org
Cc: berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 4/4] hxtool: Error on missing docs
Date: Thu, 15 Jan 2026 13:17:11 +0100 [thread overview]
Message-ID: <87tswnvznc.fsf@pond.sub.org> (raw)
In-Reply-To: <20260115020423.722069-5-dave@treblig.org> (dave@treblig.org's message of "Thu, 15 Jan 2026 02:04:23 +0000")
dave@treblig.org writes:
> From: "Dr. David Alan Gilbert" <dave@treblig.org>
>
> Error if a '.name' is seen after another '.name' without an intervening
> SRST, this normally indicates missing or misplaced docs.
>
> We can't check DEF (as used in command line options) because those
> often have multiple DEF per doc.
Pity.
> Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
> ---
> scripts/hxtool | 20 +++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/hxtool b/scripts/hxtool
> index ea2accef98..f310071daa 100755
> --- a/scripts/hxtool
> +++ b/scripts/hxtool
> @@ -1,8 +1,14 @@
> #!/bin/sh
>
> +printifnotrst()
print_if_not_rst()? print_h()?
> +{
> + test $outsiderst -eq 1 && printf "%s\n" "$str"
> +}
> hxtoh()
> {
> outsiderst=1
> + # .name for HMP
> + seenname=0
I'd prefer seen_name.
> while read -r str; do
> case $str in
> HXCOMM*)
> @@ -13,6 +19,8 @@ hxtoh()
> echo "Error: SRST inside another RST" >&2
> exit 1
> fi
> + # consume the name
> + seenname=0
> outsiderst=0
> ;;
> ERST*)
> @@ -23,8 +31,18 @@ hxtoh()
> fi
> outsiderst=1
> ;;
> + # Note the space at the start - we need to exclude something.name
> + .name*)
This works?!? It does in my testing. I'm amazed.
> + if [ $seenname -eq 1 ]
> + then
> + echo "Error: Seen another .name, maybe missing docs?" >&2
> + exit 1
> + fi
> + seenname=1
> + printifnotrst
> + ;;
> *)
> - test $outsiderst -eq 1 && printf "%s\n" "$str"
> + printifnotrst
> ;;
> esac
> done
Could move the printing behind the case, and continue the loop in the
case SRST* and ERST*. No need for the function then. Matter of taste,
up to you.
next prev parent reply other threads:[~2026-01-15 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 2:04 [PATCH 0/4] HMP: hxtool sanity checks dave
2026-01-15 2:04 ` [PATCH 1/4] hmp-commands-info.hx: Move definition of "info accel" dave
2026-01-15 2:04 ` [PATCH 2/4] hmp*hx: Move info docs dave
2026-01-15 11:57 ` Markus Armbruster
2026-01-15 18:42 ` Dr. David Alan Gilbert
2026-01-16 8:45 ` Markus Armbruster
2026-01-15 2:04 ` [PATCH 3/4] hxtool: Split srst/erst add checks dave
2026-01-15 12:11 ` Markus Armbruster
2026-01-15 2:04 ` [PATCH 4/4] hxtool: Error on missing docs dave
2026-01-15 12:17 ` Markus Armbruster [this message]
2026-01-15 12:43 ` Dr. David Alan Gilbert
2026-01-15 11:15 ` [PATCH 0/4] HMP: hxtool sanity checks Marc-André Lureau
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=87tswnvznc.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dave@treblig.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.