From: Laszlo Ersek <lersek@redhat.com>
To: peter.maydell@linaro.org
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>,
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
Cornelia Huck <cohuck@redhat.com>, Michael Clark <mjc@sifive.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.12.0-rc4 is now available
Date: Tue, 24 Apr 2018 14:46:27 +0200 [thread overview]
Message-ID: <6bb9731f-013d-018d-0b6e-c6dc55570f1f@redhat.com> (raw)
In-Reply-To: <152406338081.5947.5696498314762417499@sif>
Hi Peter,
On 04/18/18 16:56, Michael Roth wrote:
> A note from the maintainer:
>
> Barring any reports of showstopper bugs, the plan is to release
> 2.12.0 with no further changes on Tuesday 24th April.
I just noticed two QAPI bugs introduced in 2.12, in the following two
commits:
(1) ca230ff33f89 ("qmp: add architecture specific cpu data for
query-cpus-fast", 2018-02-26)
This commit added @arch to @CpuInfoFast, but it failed to set the new
field to CPU_INFO_ARCH_OTHER in qmp_query_cpus_fast(), when TARGET_S390X
is not defined.
(2) 25fa194b7b11 ("RISC-V Build Infrastructure", 2018-03-07)
This commit added the @riscv enum constant to @CpuInfoArch (used in both
@CpuInfo and @CpuInfoFast -- the return types of the @query-cpus and
@query-cpus-fast commands, respectively), and assigned, in both return
structures, the @CpuInfoRISCV sub-structure to the new enum value.
However, qmp_query_cpus_fast() does not populate the sub-structure, when
TARGET_RISCV is defined; only qmp_query_cpus() does.
The fixes don't look complicated. Do you want to hold the release while
I post the fixes?
I don't think these bugs are "show stoppers". On the other hand, QAPI is
an external interface.
Thanks
Laszlo
next prev parent reply other threads:[~2018-04-24 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 14:56 [Qemu-devel] [ANNOUNCE] QEMU 2.12.0-rc4 is now available Michael Roth
2018-04-24 12:46 ` Laszlo Ersek [this message]
2018-04-24 13:39 ` Eric Blake
2018-04-24 13:56 ` Laszlo Ersek
2018-04-24 15:24 ` Cornelia Huck
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=6bb9731f-013d-018d-0b6e-c6dc55570f1f@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=mjc@sifive.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).