From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH v4 0/6] build spice chardevs as module
Date: Wed, 30 Sep 2020 13:28:58 +0200 [thread overview]
Message-ID: <20200930112904.24397-1-kraxel@redhat.com> (raw)
v3:
- fix spice-app
- init objects before spice
- meson cleanup
v4:
- rebase to latestg master, adapt to qom changes.
- add patches to fix modular builds.
- pick up review tags.
Gerd Hoffmann (6):
ui/spice-app: don't use qemu_chr_open_spice_port directly
chardev/spice: make qemu_chr_open_spice_port static
chardev/spice: simplify chardev setup
meson: add spice_headers dependency.
meson: add spice dependency to core spice source files.
chardev/spice: build spice chardevs as module
include/chardev/spice.h | 4 ----
include/ui/qemu-spice.h | 1 -
chardev/spice.c | 37 ++++++++++---------------------------
softmmu/vl.c | 9 +++++----
ui/spice-app.c | 34 ++++++++++++++++++++++------------
ui/spice-core.c | 2 --
util/module.c | 2 ++
audio/meson.build | 2 +-
chardev/meson.build | 7 ++++++-
meson.build | 2 ++
monitor/meson.build | 2 +-
ui/meson.build | 2 +-
12 files changed, 50 insertions(+), 54 deletions(-)
--
2.27.0
next reply other threads:[~2020-09-30 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 11:28 Gerd Hoffmann [this message]
2020-09-30 11:28 ` [PATCH v4 1/6] ui/spice-app: don't use qemu_chr_open_spice_port directly Gerd Hoffmann
2020-09-30 11:29 ` [PATCH v4 2/6] chardev/spice: make qemu_chr_open_spice_port static Gerd Hoffmann
2020-09-30 11:29 ` [PATCH v4 3/6] chardev/spice: simplify chardev setup Gerd Hoffmann
2020-09-30 11:29 ` [PATCH v4 4/6] meson: add spice_headers dependency Gerd Hoffmann
2020-09-30 11:29 ` [PATCH v4 5/6] meson: add spice dependency to core spice source files Gerd Hoffmann
2020-09-30 11:29 ` [PATCH v4 6/6] chardev/spice: build spice chardevs as module Gerd Hoffmann
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=20200930112904.24397-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=marcandre.lureau@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).