qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, anthony@codemonkey.ws
Subject: [Qemu-devel] [PULL 0/8] Block patches for 2.0.0-rc1
Date: Wed, 19 Mar 2014 14:11:59 +0100	[thread overview]
Message-ID: <1395234727-6841-1-git-send-email-kwolf@redhat.com> (raw)

The following changes since commit 059b3527f0229f4d60fd77a317503d42abd5e50f:

  Merge remote-tracking branch 'remotes/kraxel/tags/pull-vnc-2' into staging (2014-03-18 16:39:29 +0000)

are available in the git repository at:


  git://repo.or.cz/qemu/kevin.git tags/for-upstream

for you to fetch changes up to 198fd05c357afff22f0b0e02639937519ed49b1f:

  dataplane: fix implicit IOThread refcount (2014-03-19 09:45:25 +0100)

----------------------------------------------------------------
Block patches for 2.0.0-rc1

----------------------------------------------------------------
Kevin Wolf (1):
      block: Add error handling to bdrv_invalidate_cache()

Maria Kustova (2):
      qemu-io-cmds: Fixed typo in example for writev.
      qemu-io: Extended "--cmd" description in usage text

Max Reitz (2):
      qcow2: Correct comment for realloc_refcount_block()
      qcow2: Fix fail path in realloc_refcount_block()

Peter Lieven (2):
      block/nfs: bump libnfs requirement to 1.9.3
      block/nfs: report errors from libnfs

Stefan Hajnoczi (1):
      dataplane: fix implicit IOThread refcount

 block.c                         | 28 ++++++++++++++++++++++------
 block/nfs.c                     |  3 +++
 block/qcow2-refcount.c          | 36 +++++++++++++++++++-----------------
 block/qcow2.c                   | 22 +++++++++++++++++++---
 block/qed.c                     | 21 ++++++++++++++++++---
 block/quorum.c                  |  9 +++++++--
 configure                       |  2 +-
 hw/block/dataplane/virtio-blk.c |  2 +-
 include/block/block.h           |  4 ++--
 include/block/block_int.h       |  2 +-
 migration.c                     |  8 +++++++-
 qemu-io-cmds.c                  |  2 +-
 qemu-io.c                       |  9 ++++++---
 13 files changed, 107 insertions(+), 41 deletions(-)

             reply	other threads:[~2014-03-19 13:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 13:11 Kevin Wolf [this message]
2014-03-19 13:12 ` [Qemu-devel] [PULL 1/8] block: Add error handling to bdrv_invalidate_cache() Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 2/8] qemu-io-cmds: Fixed typo in example for writev Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 3/8] qemu-io: Extended "--cmd" description in usage text Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 4/8] qcow2: Correct comment for realloc_refcount_block() Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 5/8] qcow2: Fix fail path in realloc_refcount_block() Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 6/8] block/nfs: bump libnfs requirement to 1.9.3 Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 7/8] block/nfs: report errors from libnfs Kevin Wolf
2014-03-19 13:12 ` [Qemu-devel] [PULL 8/8] dataplane: fix implicit IOThread refcount Kevin Wolf
2014-03-19 14:16 ` [Qemu-devel] [PULL 0/8] Block patches for 2.0.0-rc1 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=1395234727-6841-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).