qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 0/4] Job API improvements and bugfixes
Date: Fri, 30 Mar 2012 13:17:09 +0200	[thread overview]
Message-ID: <1333106233-12472-1-git-send-email-pbonzini@redhat.com> (raw)

This patch includes a few small changes to the job API.  Do not be
fooled by the diffstat, since that is mostly due to the new documentation
in patch 4.

Patch 3 has a small change to the BlockJobType interface, because I
found hard to document the old one.

Paolo Bonzini (4):
  block: cancel jobs when a device is ready to go away
  block: fix streaming/closing race
  block: set job->speed in block_set_speed
  block: document job API

 block.c        |   24 +++++++++++-
 block/stream.c |    7 ++-
 block_int.h    |  117 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 blockdev.c     |    3 +
 4 files changed, 144 insertions(+), 7 deletions(-)

-- 
1.7.9.1

             reply	other threads:[~2012-03-30 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 11:17 Paolo Bonzini [this message]
2012-03-30 11:17 ` [Qemu-devel] [PATCH 1/4] block: cancel jobs when a device is ready to go away Paolo Bonzini
2012-04-02 15:38   ` Kevin Wolf
2012-03-30 11:17 ` [Qemu-devel] [PATCH 2/4] block: fix streaming/closing race Paolo Bonzini
2012-03-30 13:32   ` Stefan Hajnoczi
2012-03-30 11:17 ` [Qemu-devel] [PATCH 3/4] block: set job->speed in block_set_speed Paolo Bonzini
2012-03-30 11:17 ` [Qemu-devel] [PATCH 4/4] block: document job API Paolo Bonzini
2012-03-30 13:42 ` [Qemu-devel] [PATCH 0/4] Job API improvements and bugfixes Stefan Hajnoczi
2012-04-02 15:41 ` Kevin Wolf

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=1333106233-12472-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).