From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: pbonzini@redhat.com, pkrempa@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] qom: Support JSON in user_creatable_parse_str()
Date: Fri, 12 Mar 2021 17:32:25 +0100 [thread overview]
Message-ID: <YEuXmXzTjCPyAn+j@merkur.fritz.box> (raw)
In-Reply-To: <87h7lg1huk.fsf@dusky.pond.sub.org>
Am 12.03.2021 um 17:01 hat Markus Armbruster geschrieben:
> Is this an alternative to Paolo's "[PATCH 0/3] vl: QAPIfy -object", and
> if not, how do the two play together?
Paolo's patch adds JSON support to the system emulator CLI (using
QemuOpts to stay compatible with the list magic), this patch adds it to
everything else (tools don't have memory-backend, and HMP isn't a stable
interface, so they all use the same keyval-based function modified by
this patch).
Kevin
next prev parent reply other threads:[~2021-03-12 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 13:19 [PATCH] qom: Support JSON in user_creatable_parse_str() Kevin Wolf
2021-03-12 13:59 ` Eric Blake
2021-03-12 14:47 ` Paolo Bonzini
2021-03-12 16:01 ` Markus Armbruster
2021-03-12 16:32 ` Kevin Wolf [this message]
2021-03-13 8:00 ` Markus Armbruster
2021-03-15 11:56 ` Kevin Wolf
2021-03-15 12:00 ` Paolo Bonzini
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=YEuXmXzTjCPyAn+j@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).