From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: samuel.thibault@ens-lyon.org
Subject: [Qemu-devel] [PATCH v2 00/21] qemu-char: refactoring of chardev creation
Date: Wed, 14 Oct 2015 17:54:21 +0200 [thread overview]
Message-ID: <1444838064-14481-1-git-send-email-pbonzini@redhat.com> (raw)
This series rewrites chardev creation to use a new ->create
member of the CharDriver struct, and to always signal errors
via Error*.
The advantage is that backend-specific creation functions need
not be exported anymore for qemu-char.c's usage, and hence do not
need stubs anymore.
Paolo Bonzini (21):
qemu-char: cleanup qmp_chardev_add
qemu-char: cleanup HAVE_CHARDEV_*
qemu-char: add create to register_char_driver
qemu-char: convert file backend to data-driven creation
qemu-char: convert serial backend to data-driven creation
qemu-char: convert parallel backend to data-driven creation
qemu-char: convert pipe backend to data-driven creation
qemu-char: convert socket backend to data-driven creation
qemu-char: convert UDP backend to data-driven creation
qemu-char: convert pty backend to data-driven creation
qemu-char: convert null backend to data-driven creation
qemu-char: convert mux backend to data-driven creation
qemu-char: convert msmouse backend to data-driven creation
qemu-char: convert braille backend to data-driven creation
qemu-char: convert testdev backend to data-driven creation
qemu-char: convert stdio backend to data-driven creation
qemu-char: convert console backend to data-driven creation
qemu-char: convert spice backend to data-driven creation
qemu-char: convert vc backend to data-driven creation
qemu-char: convert ringbuf backend to data-driven creation
qemu-char: cleanup after completed conversion to cd->create
backends/baum.c | 17 +-
backends/msmouse.c | 8 +-
backends/testdev.c | 8 +-
include/sysemu/char.h | 18 +-
include/ui/qemu-spice.h | 2 -
qemu-char.c | 392 ++++++++++++++++++++++++--------------------
spice-qemu-char.c | 21 ++-
stubs/Makefile.objs | 5 -
stubs/chr-baum-init.c | 7 -
stubs/chr-msmouse.c | 7 -
stubs/chr-testdev.c | 7 -
stubs/qemu-chr-open-spice.c | 14 --
stubs/vc-init.c | 7 -
ui/console.c | 11 +-
ui/gtk.c | 2 +-
15 files changed, 260 insertions(+), 266 deletions(-)
delete mode 100644 stubs/chr-baum-init.c
delete mode 100644 stubs/chr-msmouse.c
delete mode 100644 stubs/chr-testdev.c
delete mode 100644 stubs/qemu-chr-open-spice.c
delete mode 100644 stubs/vc-init.c
--
2.5.0
next reply other threads:[~2015-10-14 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 15:54 Paolo Bonzini [this message]
2015-10-14 15:54 ` [Qemu-devel] [PATCH v2 06/21] qemu-char: convert parallel backend to data-driven creation Paolo Bonzini
2015-10-14 20:52 ` Eric Blake
2015-10-14 15:54 ` [Qemu-devel] [PATCH v2 07/21] qemu-char: convert pipe " Paolo Bonzini
2015-10-14 20:53 ` Eric Blake
2015-10-14 15:54 ` [Qemu-devel] [PATCH v2 14/21] qemu-char: convert braille " Paolo Bonzini
2015-10-14 20:53 ` Eric Blake
2015-10-14 16:18 ` [Qemu-devel] [PATCH v2 00/21] qemu-char: refactoring of chardev creation Eric Blake
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=1444838064-14481-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).