qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: anthony@codemonkey.ws
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/9] Block patches
Date: Wed, 16 Mar 2011 11:47:52 +0100	[thread overview]
Message-ID: <1300272481-8744-1-git-send-email-kwolf@redhat.com> (raw)

The following changes since commit cc015e9a5dde2f03f123357fa060acbdfcd570a4:

  add Win32 IPI service (2011-03-13 14:44:22 +0000)

are available in the git repository at:
  git://repo.or.cz/qemu/kevin.git for-anthony

Brian Wheeler (1):
      Fix ATA SMART and CHECK POWER MODE

Feiran Zheng (1):
      hw/xen_disk: aio_inflight not released in handling ioreq when nr_segments==0

Jes Sorensen (1):
      Improve error handling in do_snapshot_blkdev()

Kevin Wolf (3):
      Add error message for loading snapshot without VM state
      tools: Use real async.c instead of stubs
      Add qcow2 documentation

Ryan Harper (1):
      Don't allow multiwrites against a block device without underlying medium

Stefan Weil (2):
      block/vdi: Don't ignore immediate read/write failures
      block/qcow: Don't ignore immediate read/write and other failures

 Makefile.objs        |    4 +-
 block.c              |    8 ++
 block/qcow.c         |   16 +++-
 block/vdi.c          |    5 +
 blockdev.c           |   23 ++++-
 docs/specs/qcow2.txt |  260 ++++++++++++++++++++++++++++++++++++++++++++++++++
 hw/ide/core.c        |   41 ++++++---
 hw/xen_disk.c        |    2 +-
 qemu-tool.c          |   47 +--------
 savevm.c             |    2 +
 10 files changed, 339 insertions(+), 69 deletions(-)
 create mode 100644 docs/specs/qcow2.txt

             reply	other threads:[~2011-03-16 10:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 10:47 Kevin Wolf [this message]
2011-03-16 10:47 ` [Qemu-devel] [PATCH 1/9] block/vdi: Don't ignore immediate read/write failures Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 2/9] block/qcow: Don't ignore immediate read/write and other failures Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 3/9] Add error message for loading snapshot without VM state Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 4/9] tools: Use real async.c instead of stubs Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 5/9] Don't allow multiwrites against a block device without underlying medium Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 6/9] Fix ATA SMART and CHECK POWER MODE Kevin Wolf
2011-03-16 10:47 ` [Qemu-devel] [PATCH 7/9] Improve error handling in do_snapshot_blkdev() Kevin Wolf
2011-03-16 10:48 ` [Qemu-devel] [PATCH 8/9] hw/xen_disk: aio_inflight not released in handling ioreq when nr_segments==0 Kevin Wolf
2011-03-16 10:48 ` [Qemu-devel] [PATCH 9/9] Add qcow2 documentation Kevin Wolf
2011-03-21 13:31 ` [Qemu-devel] Re: [PULL 0/9] Block patches Kevin Wolf
2011-03-21 20:43   ` Aurelien Jarno
  -- strict thread matches above, loose matches on Subject: below --
2013-03-04  9:15 [Qemu-devel] " Stefan Hajnoczi
2014-02-28 18:33 Stefan Hajnoczi
2014-03-04 17:02 ` Peter Maydell
2016-06-28 13:23 Stefan Hajnoczi
2016-06-28 14:03 ` Peter Maydell
2017-02-21 15:40 Jeff Cody
2017-02-21 18:16 ` Peter Maydell
2019-02-11  5:50 Stefan Hajnoczi
2019-02-11 11:42 ` 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=1300272481-8744-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).