All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Markus Armbruster" <armbru@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Zhong, Yang" <yang.zhong@intel.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 00/12] Machine and OS X changes for 2021-06-08
Date: Thu, 10 Jun 2021 15:11:04 +0200	[thread overview]
Message-ID: <8101172b-97b1-f61b-f513-53afc7e3dca0@redhat.com> (raw)
In-Reply-To: <87czsugtr7.fsf@dusky.pond.sub.org>

On 10/06/21 07:42, Markus Armbruster wrote:
>>> ----------------------------------------------------------------
>>> Paolo Bonzini (12):
>>>        qom: export more functions for use with non-UserCreatable objects
>>>        keyval: introduce keyval_merge
>>>        keyval: introduce keyval_parse_into
>>>        vl: switch -M parsing to keyval
>>>        qemu-option: remove now-dead code
>>>        machine: move dies from X86MachineState to CpuTopology
>>>        machine: move common smp_parse code to caller
>>>        machine: add error propagation to mc->smp_parse
>>>        machine: pass QAPI struct to mc->smp_parse
>>>        machine: reject -smp dies!=1 for non-PC machines
>>>        machine: add smp compound property
>>>        vnc: avoid deprecation warnings for SASL on OS X
>>
>> None of these changes have any reviewed-by tags.

All of them however have been on the list for one to six months; the 
most recent post is 
https://patchew.org/QEMU/20210513162901.1310239-1-pbonzini@redhat.com/, 
but indeed I haven't posted a new version after rebasing on top of the 
recent -object bugfixes.

> PATCH 03 looks unfamiliar, so I checked: it hasn't been posted before.

The code was posted for the first time 6 months ago 
(https://patchew.org/QEMU/20201202090305.4129317-1-pbonzini@redhat.com/20201202090305.4129317-18-pbonzini@redhat.com/), 
though parts of it have been progressively separated and merged.  But 
indeed, the part that's left and that is included in this pull request 
hasn't been posted separately.  I'll do so now.

> Seems likely; I very much doubt Paolo would be trying to pull a fast one
> on us ;)

Not voluntarily, at least!  Sorry about that, I mis-remembered the order 
of the two series (which is now getting a bit more urgent, because Yang 
Zhong would like to use array properties in -M for SGX).

Thanks,

Paolo



  reply	other threads:[~2021-06-10 13:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  9:40 [PULL 00/12] Machine and OS X changes for 2021-06-08 Paolo Bonzini
2021-06-08  9:40 ` [PULL 01/12] qom: export more functions for use with non-UserCreatable objects Paolo Bonzini
2021-06-08  9:40 ` [PULL 02/12] keyval: introduce keyval_merge Paolo Bonzini
2021-06-08  9:40 ` [PULL 03/12] keyval: introduce keyval_parse_into Paolo Bonzini
2021-06-08  9:40 ` [PULL 04/12] vl: switch -M parsing to keyval Paolo Bonzini
2021-06-08  9:40 ` [PULL 05/12] qemu-option: remove now-dead code Paolo Bonzini
2021-06-08  9:40 ` [PULL 06/12] machine: move dies from X86MachineState to CpuTopology Paolo Bonzini
2021-06-08  9:40 ` [PULL 07/12] machine: move common smp_parse code to caller Paolo Bonzini
2021-06-08  9:40 ` [PULL 08/12] machine: add error propagation to mc->smp_parse Paolo Bonzini
2021-06-08  9:40 ` [PULL 09/12] machine: pass QAPI struct " Paolo Bonzini
2021-06-08  9:40 ` [PULL 10/12] machine: reject -smp dies!=1 for non-PC machines Paolo Bonzini
2021-06-08  9:40 ` [PULL 11/12] machine: add smp compound property Paolo Bonzini
2021-06-08  9:40 ` [PULL 12/12] vnc: avoid deprecation warnings for SASL on OS X Paolo Bonzini
2021-06-08  9:57 ` [PULL 00/12] Machine and OS X changes for 2021-06-08 Daniel P. Berrangé
2021-06-10  5:42   ` Markus Armbruster
2021-06-10 13:11     ` Paolo Bonzini [this message]
2021-06-09 14:25 ` no-reply

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=8101172b-97b1-f61b-f513-53afc7e3dca0@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yang.zhong@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.