From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/7] Misc refactoring to util codebase
Date: Tue, 20 Oct 2015 16:38:11 +0100 [thread overview]
Message-ID: <20151020153811.GP14616@redhat.com> (raw)
In-Reply-To: <1445355242-4397-1-git-send-email-berrange@redhat.com>
On Tue, Oct 20, 2015 at 04:33:55PM +0100, Daniel P. Berrange wrote:
> The following changes since commit c14e42d7a4495ecbad7bf8b3d603272e3a8992a1:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/pull-usb-20151020-1' into staging (2015-10-20 10:52:56 +0100)
>
> are available in the git repository at:
>
> https://github.com/berrange/qemu.git io-channel-3-pull
Sorry, that should be referring to the signed tag rather than the
branch name:
https://github.com/berrange/qemu.git tags/io-channel-3-for-upstream
>
> for you to fetch changes up to 88c5f205fa4c095db4c50eb7ad72816140206819:
>
> util: pull Buffer code out of VNC module (2015-10-20 14:59:09 +0100)
>
> ----------------------------------------------------------------
>
> Daniel P. Berrange (7):
> sockets: add helpers for creating SocketAddress from a socket
> sockets: move qapi_copy_SocketAddress into qemu-sockets.c
> sockets: allow port to be NULL when listening on IP address
> ui: convert VNC startup code to use SocketAddress
> osdep: add qemu_fork() wrapper for safely handling signals
> coroutine: move into libqemuutil.a library
> util: pull Buffer code out of VNC module
>
> MAINTAINERS | 13 ++
> Makefile.objs | 4 -
> block.c | 2 +-
> block/qcow2.h | 2 +-
> block/vdi.c | 2 +-
> block/write-threshold.c | 2 +-
> blockjob.c | 2 +-
> hw/9pfs/codir.c | 2 +-
> hw/9pfs/cofile.c | 2 +-
> hw/9pfs/cofs.c | 2 +-
> hw/9pfs/coxattr.c | 2 +-
> hw/9pfs/virtio-9p-coth.c | 2 +-
> hw/9pfs/virtio-9p-coth.h | 2 +-
> hw/9pfs/virtio-9p.h | 2 +-
> include/block/block.h | 2 +-
> include/block/block_int.h | 2 +-
> include/qemu/buffer.h | 118 ++++++++++++
> include/{block => qemu}/coroutine.h | 0
> include/{block => qemu}/coroutine_int.h | 2 +-
> include/qemu/osdep.h | 16 ++
> include/qemu/sockets.h | 34 ++++
> migration/qemu-file-buf.c | 2 +-
> migration/qemu-file-stdio.c | 2 +-
> migration/qemu-file-unix.c | 2 +-
> migration/qemu-file.c | 2 +-
> migration/rdma.c | 2 +-
> nbd.c | 2 +-
> qapi-schema.json | 6 +-
> qemu-char.c | 25 ---
> tests/test-coroutine.c | 4 +-
> tests/test-vmstate.c | 2 +-
> thread-pool.c | 2 +-
> ui/vnc.c | 203 +++++++++------------
> ui/vnc.h | 16 +-
> util/Makefile.objs | 4 +
> util/buffer.c | 65 +++++++
> coroutine-gthread.c => util/coroutine-gthread.c | 2 +-
> .../coroutine-sigaltstack.c | 2 +-
> coroutine-ucontext.c => util/coroutine-ucontext.c | 2 +-
> coroutine-win32.c => util/coroutine-win32.c | 2 +-
> util/oslib-posix.c | 71 +++++++
> util/oslib-win32.c | 9 +
> qemu-coroutine-io.c => util/qemu-coroutine-io.c | 2 +-
> .../qemu-coroutine-lock.c | 4 +-
> .../qemu-coroutine-sleep.c | 2 +-
> qemu-coroutine.c => util/qemu-coroutine.c | 4 +-
> util/qemu-sockets.c | 158 +++++++++++++++-
> 47 files changed, 613 insertions(+), 199 deletions(-)
> create mode 100644 include/qemu/buffer.h
> rename include/{block => qemu}/coroutine.h (100%)
> rename include/{block => qemu}/coroutine_int.h (98%)
> create mode 100644 util/buffer.c
> rename coroutine-gthread.c => util/coroutine-gthread.c (99%)
> rename coroutine-sigaltstack.c => util/coroutine-sigaltstack.c (99%)
> rename coroutine-ucontext.c => util/coroutine-ucontext.c (99%)
> rename coroutine-win32.c => util/coroutine-win32.c (98%)
> rename qemu-coroutine-io.c => util/qemu-coroutine-io.c (99%)
> rename qemu-coroutine-lock.c => util/qemu-coroutine-lock.c (98%)
> rename qemu-coroutine-sleep.c => util/qemu-coroutine-sleep.c (96%)
> rename qemu-coroutine.c => util/qemu-coroutine.c (98%)
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-10-20 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 15:33 [Qemu-devel] [PULL 0/7] Misc refactoring to util codebase Daniel P. Berrange
2015-10-20 15:33 ` [Qemu-devel] [PULL 1/7] sockets: add helpers for creating SocketAddress from a socket Daniel P. Berrange
2015-10-20 15:33 ` [Qemu-devel] [PULL 2/7] sockets: move qapi_copy_SocketAddress into qemu-sockets.c Daniel P. Berrange
2015-10-20 15:33 ` [Qemu-devel] [PULL 3/7] sockets: allow port to be NULL when listening on IP address Daniel P. Berrange
2015-10-20 15:33 ` [Qemu-devel] [PULL 4/7] ui: convert VNC startup code to use SocketAddress Daniel P. Berrange
2015-10-20 15:34 ` [Qemu-devel] [PULL 5/7] osdep: add qemu_fork() wrapper for safely handling signals Daniel P. Berrange
2015-10-20 15:34 ` [Qemu-devel] [PULL 6/7] coroutine: move into libqemuutil.a library Daniel P. Berrange
2015-10-20 15:34 ` [Qemu-devel] [PULL 7/7] util: pull Buffer code out of VNC module Daniel P. Berrange
2015-10-20 15:38 ` [Qemu-devel] [PULL 0/7] Misc refactoring to util codebase Peter Maydell
2015-10-20 15:38 ` Daniel P. Berrange [this message]
2015-10-21 12:27 ` 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=20151020153811.GP14616@redhat.com \
--to=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).