From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [PATCH v2 0/3] vl: QAPIfy -object
Date: Tue, 16 Mar 2021 18:31:47 +0100 [thread overview]
Message-ID: <YFDrg8r6yK7BwN2z@merkur.fritz.box> (raw)
In-Reply-To: <20210312173547.1283477-1-pbonzini@redhat.com>
Am 12.03.2021 um 18:35 hat Paolo Bonzini geschrieben:
> This is a replacement for -object QAPIfication that keeps QemuOpts
> in order to not break some of the CLI parsing extensions that OptsVisitor
> includes. Since keyval is not used, support for directly passing
> JSON syntax to the option must be added manually, which is what patch
> 3 does. However, both the QemuOpts and the JSON paths go through
> the new ObjectOptions interface, just with two different visitors,
> so we can reuse all the new type-safe code that Kevin has added.
>
> Patch 1 is a patch that I already had lying around, which I included
> to be able to remove user_creatable_add_opts completely in patch 2.
>
> Paolo
>
> Based-on: <20210311144811.313451-1-kwolf@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2021-03-16 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 17:35 [PATCH v2 0/3] vl: QAPIfy -object Paolo Bonzini
2021-03-12 17:35 ` [PATCH v2 1/3] tests: convert check-qom-proplist to keyval Paolo Bonzini
2021-03-12 17:35 ` [PATCH v2 2/3] qom: move user_creatable_add_opts logic to vl.c and QAPIfy it Paolo Bonzini
2021-03-17 11:48 ` Kevin Wolf
2021-04-12 16:53 ` David Hildenbrand
2021-04-13 4:41 ` Markus Armbruster
2021-04-13 8:13 ` David Hildenbrand
2021-04-13 8:33 ` David Hildenbrand
2021-04-13 9:38 ` Kevin Wolf
2021-04-13 9:48 ` Markus Armbruster
2021-04-16 14:56 ` Paolo Bonzini
2021-03-12 17:35 ` [PATCH v2 3/3] vl: allow passing JSON to -object Paolo Bonzini
2021-03-16 17:31 ` Kevin Wolf [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=YFDrg8r6yK7BwN2z@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@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).