qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: mreitz@redhat.com, den@openvz.org, jcody@redhat.com,
	eblake@redhat.com, berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.12 v2 00/12] block: Follow-up for .bdrv_co_create (part 1)
Date: Mon, 26 Mar 2018 12:18:51 +0200	[thread overview]
Message-ID: <20180326101851.GA5267@localhost.localdomain> (raw)
In-Reply-To: <20180321173714.14741-1-kwolf@redhat.com>

Am 21.03.2018 um 18:37 hat Kevin Wolf geschrieben:
> This series adds qemu-iotests for a few more block drivers (yet more to
> come in another series) and fixes a few things that previous review and
> these tests brought up.
> 
> The only major design change is that I converted the vdi block driver
> from a boolean 'static' create option to the standard 'preallocation'
> one that other drivers are using. This seems like a good move to make
> while the interface isn't stable yet.
> 
> v2:
> - Patch 1: Mention allowed values for 'preallocation' [Eric]
> - Patch 3: Fixed comments, removed 2^63-512 case [Eric]
> - Patch 6: Added missing reference output change [Eric]
> - Patch 7: s/UINT64_MAX/INT64_MAX/ [Eric]
> - Patches 8 and 12: Fixed comments [Eric]

Applied to the block branch.

Kevin

      parent reply	other threads:[~2018-03-26 10:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 17:37 [Qemu-devel] [PATCH for-2.12 v2 00/12] block: Follow-up for .bdrv_co_create (part 1) Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 01/12] vdi: Change 'static' create option to 'preallocation' in QMP Kevin Wolf
2018-03-21 17:41   ` Eric Blake
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 02/12] vdi: Fix build with CONFIG_VDI_DEBUG Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 03/12] qemu-iotests: Test vdi image creation with QMP Kevin Wolf
2018-03-23 21:43   ` Eric Blake
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 04/12] qemu-iotests: Enable 025 for luks Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 05/12] luks: Turn another invalid assertion into check Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 06/12] qemu-iotests: Test invalid resize on luks Kevin Wolf
2018-03-23 21:49   ` Eric Blake
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 07/12] parallels: Check maximum cluster size on create Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 08/12] qemu-iotests: Test parallels image creation with QMP Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 09/12] vhdx: Require power-of-two block size on create Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 10/12] vhdx: Don't use error_setg_errno() with constant errno Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 11/12] vhdx: Check for 4 GB maximum log size on creation Kevin Wolf
2018-03-21 17:37 ` [Qemu-devel] [PATCH for-2.12 v2 12/12] qemu-iotests: Test vhdx image creation with QMP Kevin Wolf
2018-03-26 10:18 ` Kevin Wolf [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=20180326101851.GA5267@localhost.localdomain \
    --to=kwolf@redhat.com \
    --cc=berrange@redhat.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.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).