From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [PULL 00/10] machine + QOM queue, 2020-10-14
Date: Wed, 14 Oct 2020 10:34:05 -0400 [thread overview]
Message-ID: <20201014143415.240472-1-ehabkost@redhat.com> (raw)
The following changes since commit 96292515c07e3a99f5a29540ed2f257b1ff75111:
Merge remote-tracking branch 'remotes/vivier2/tags/trivial-branch-for-5.2-pull-request' into staging (2020-10-13 14:06:22 +0100)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/machine-next-pull-request
for you to fetch changes up to d9753cca6b0db724bc6d15e60cfad1705f800b96:
can-host-socketcan: Fix crash when 'if' option is not set (2020-10-13 15:56:30 -0400)
----------------------------------------------------------------
machine + QOM queue, 2020-10-14
* Register some properties as class properties (Eduardo Habkost)
* authz-list-file: Fix crash when filename is not set (Eduardo Habkost)
* can-host-socketcan: Fix crash when 'if' option is not set (Eduardo Habkost)
----------------------------------------------------------------
Eduardo Habkost (10):
rng-egd: Register "chardev" as class property
rng-random: register "filename" as class property
rng: Register "opened" as class property
input-linux: Register properties as class properties
input-barrier: Register properties as class properties
i386: Register most CPU properties as class properties
vga-pci: Register "big-endian-framebuffer" as class property
vhost-user: Register "chardev" as class property
authz-list-file: Fix crash when filename is not set
can-host-socketcan: Fix crash when 'if' option is not set
authz/listfile.c | 5 ++++
backends/rng-egd.c | 9 ++----
backends/rng-random.c | 8 ++---
backends/rng.c | 8 ++---
backends/vhost-user.c | 6 ++--
hw/display/vga-pci.c | 12 +++-----
net/can/can_socketcan.c | 5 ++++
target/i386/cpu.c | 66 +++++++++++++++++++++--------------------
ui/input-barrier.c | 44 +++++++++++++--------------
ui/input-linux.c | 27 +++++++++--------
10 files changed, 97 insertions(+), 93 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-14 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 14:34 Eduardo Habkost [this message]
2020-10-14 14:34 ` [PULL 01/10] rng-egd: Register "chardev" as class property Eduardo Habkost
2020-10-14 14:34 ` [PULL 02/10] rng-random: register "filename" " Eduardo Habkost
2020-10-14 14:34 ` [PULL 03/10] rng: Register "opened" " Eduardo Habkost
2020-10-14 14:34 ` [PULL 04/10] input-linux: Register properties as class properties Eduardo Habkost
2020-10-14 14:34 ` [PULL 05/10] input-barrier: " Eduardo Habkost
2020-10-14 14:34 ` [PULL 06/10] i386: Register most CPU " Eduardo Habkost
2020-10-14 14:34 ` [PULL 07/10] vga-pci: Register "big-endian-framebuffer" as class property Eduardo Habkost
2020-10-14 14:34 ` [PULL 08/10] vhost-user: Register "chardev" " Eduardo Habkost
2020-10-14 14:34 ` [PULL 09/10] authz-list-file: Fix crash when filename is not set Eduardo Habkost
2020-10-14 14:34 ` [PULL 10/10] can-host-socketcan: Fix crash when 'if' option " Eduardo Habkost
2020-10-15 19:30 ` [PULL 00/10] machine + QOM queue, 2020-10-14 Peter Maydell
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=20201014143415.240472-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).