qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv2 6/6] block: fix qemu-iotest reference output for test 067
Date: Thu, 23 Oct 2014 12:03:20 +0200	[thread overview]
Message-ID: <5448D268.8070105@redhat.com> (raw)
In-Reply-To: <1413984120-21830-7-git-send-email-pl@kamp.de>

On 2014-10-22 at 15:22, Peter Lieven wrote:
> Output is changed by the addition of the write-merging parameter
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
>   tests/qemu-iotests/067.out |   10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)

Reviewed-by: Max Reitz <mreitz@redhat.com>

      reply	other threads:[~2014-10-23 10:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 13:21 [Qemu-devel] [PATCHv2 0/6] multiwrite patches for 2.2 Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 1/6] block: add accounting for merged requests Peter Lieven
2014-10-22 18:20   ` Eric Blake
2014-10-22 20:22     ` Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 2/6] block: introduce bdrv_runtime_opts Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 3/6] block: add a knob to disable multiwrite_merge Peter Lieven
2014-10-22 18:29   ` Eric Blake
2014-10-22 20:24     ` Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 4/6] hw/virtio-blk: add a constant for max number of merged requests Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 5/6] block: add qemu-iotest for write-merge parameter Peter Lieven
2014-10-23  9:59   ` Max Reitz
2014-10-22 13:22 ` [Qemu-devel] [PATCHv2 6/6] block: fix qemu-iotest reference output for test 067 Peter Lieven
2014-10-23 10:03   ` Max Reitz [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=5448D268.8070105@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).