From: Juan Quintela <quintela@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qemu-file: Move QEMUFileOps implementations to separate files
Date: Tue, 14 Oct 2014 10:30:40 +0200 [thread overview]
Message-ID: <87bnpfm4sv.fsf@elfo.elfo> (raw)
In-Reply-To: <1412195677-24529-1-git-send-email-ehabkost@redhat.com> (Eduardo Habkost's message of "Wed, 1 Oct 2014 17:34:33 -0300")
Eduardo Habkost <ehabkost@redhat.com> wrote:
> 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
Reviewed-by: Juan Quintela <quintela@redhat.com>
Applied. Minor conflicts with David qemu-file on buffer on Makefiles
handled by me.
prev parent reply other threads:[~2014-10-14 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:34 [Qemu-devel] [PATCH 0/4] qemu-file: Move QEMUFileOps implementations to separate files Eduardo Habkost
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 [this message]
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=87bnpfm4sv.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=ehabkost@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 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.