From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, qemu-trivial@nongnu.org
Subject: Re: [PATCH] json-parser: fix formatting of comment
Date: Mon, 13 Jul 2026 14:32:47 +0200 [thread overview]
Message-ID: <87ik6jgjdc.fsf@pond.sub.org> (raw)
In-Reply-To: <20260713114622.1950506-1-pbonzini@redhat.com> (Paolo Bonzini's message of "Mon, 13 Jul 2026 13:46:22 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> qobject/json-parser.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/qobject/json-parser.c b/qobject/json-parser.c
> index 5935730c0c7..6b1b4762bda 100644
> --- a/qobject/json-parser.c
> +++ b/qobject/json-parser.c
> @@ -29,9 +29,10 @@
> * object, an error, or NULL (if the object is incomplete and no error
> * happened) after every token. Therefore it has an explicit
> * representation of its parser stack; each stack entry consists of a
> - * parser state and a QObject: - a QList, for an array that is being
> - * added to - a QDict, for a dictionary that is being added to - a
> - * QString, for the key of the next pair that will be added to a QDict
> + * parser state and a QObject:
> + * - a QList, for an array that is being added to
> + * - a QDict, for a dictionary that is being added to
> + * - a QString, for the key of the next pair that will be added to a QDict
> *
> * The stack represents an arbitrary nesting of arrays and dictionaries
> * (whose next key has been parsed); it can also have a dictionary whose
I screwed this up. My apologies!
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Queued for 11.1. Thanks!
prev parent reply other threads:[~2026-07-13 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:46 [PATCH] json-parser: fix formatting of comment Paolo Bonzini
2026-07-13 12:16 ` Daniel P. Berrangé
2026-07-13 12:32 ` Markus Armbruster [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=87ik6jgjdc.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox