From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] qemu-file: Move QEMUFileOps implementations to separate files
Date: Wed, 1 Oct 2014 17:34:33 -0300 [thread overview]
Message-ID: <1412195677-24529-1-git-send-email-ehabkost@redhat.com> (raw)
With this, code that uses symbols from qemu-file.c don't need to bring extra
dependencies because of the actual QEMUFile operation implementations.
Eduardo Habkost (4):
qemu-file: Make qemu_file_is_writable() non-static
qemu-file: Use qemu_file_is_writable() on stdio_fclose()
qemu-file: Move unix and socket implementations to qemu-file-unix.c
qemu-file: Move stdio implementation to qemu-file-stdio.c
Makefile.objs | 2 +-
include/migration/qemu-file.h | 1 +
qemu-file-stdio.c | 194 ++++++++++++++++++++++
qemu-file-unix.c | 223 ++++++++++++++++++++++++++
qemu-file.c | 365 +-----------------------------------------
tests/Makefile | 2 +-
6 files changed, 421 insertions(+), 366 deletions(-)
create mode 100644 qemu-file-stdio.c
create mode 100644 qemu-file-unix.c
--
1.9.3
next reply other threads:[~2014-10-01 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:34 Eduardo Habkost [this message]
2014-10-01 20:34 ` [Qemu-devel] [PATCH 1/4] qemu-file: Make qemu_file_is_writable() non-static Eduardo Habkost
2014-10-01 20:34 ` [Qemu-devel] [PATCH 2/4] qemu-file: Use qemu_file_is_writable() on stdio_fclose() Eduardo Habkost
2014-10-01 20:34 ` [Qemu-devel] [PATCH 3/4] qemu-file: Move unix and socket implementations to qemu-file-unix.c Eduardo Habkost
2014-10-01 20:34 ` [Qemu-devel] [PATCH 4/4] qemu-file: Move stdio implementation to qemu-file-stdio.c Eduardo Habkost
2014-10-02 6:49 ` [Qemu-devel] [PATCH 0/4] qemu-file: Move QEMUFileOps implementations to separate files Markus Armbruster
2014-10-02 12:37 ` Eduardo Habkost
2014-10-14 8:30 ` Juan Quintela
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=1412195677-24529-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).