From: Michal Privoznik <mprivozn@redhat.com>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, ehabkost@redhat.com, armbru@redhat.com
Subject: [PATCH v2 0/2] qmp: Expose MachineClass::default_ram_id
Date: Tue, 26 May 2020 10:25:33 +0200 [thread overview]
Message-ID: <cover.1590481402.git.mprivozn@redhat.com> (raw)
v2 of:
https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg07103.html
diff to v1:
- in 2/2 I made the default-ram-id optional, because as it turns out,
not every machine type has it set.
Michal Privoznik (2):
qapi: Fix comment format for @CpuInstanceProperties
qmp: Expose MachineClass::default_ram_id
hw/core/machine-qmp-cmds.c | 4 ++++
qapi/machine.json | 8 ++++++--
2 files changed, 10 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-26 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 8:25 Michal Privoznik [this message]
2020-05-26 8:25 ` [PATCH v2 1/2] qapi: Fix comment format for @CpuInstanceProperties Michal Privoznik
2020-05-26 13:11 ` Igor Mammedov
2020-05-26 8:25 ` [PATCH v2 2/2] qmp: Expose MachineClass::default_ram_id Michal Privoznik
2020-05-26 13:15 ` Igor Mammedov
2020-05-26 13:17 ` Igor Mammedov
2020-07-27 18:41 ` [PATCH v2 0/2] " Eduardo Habkost
2020-07-28 8:05 ` Michal Privoznik
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=cover.1590481402.git.mprivozn@redhat.com \
--to=mprivozn@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@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).