From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] iotests: Fixes to 156 and 186
Date: Thu, 27 Jul 2017 14:24:25 +0200 [thread overview]
Message-ID: <20170727122425.GC4767@localhost.localdomain> (raw)
In-Reply-To: <20170725155644.20214-1-mreitz@redhat.com>
Am 25.07.2017 um 17:56 hat Max Reitz geschrieben:
> This series contains some small fixes for issues I stumbled upon when
> preparing my pull request.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2017-07-27 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 15:56 [Qemu-devel] [PATCH 0/2] iotests: Fixes to 156 and 186 Max Reitz
2017-07-25 15:56 ` [Qemu-devel] [PATCH 1/2] iotests: Fix test 156 Max Reitz
2017-07-25 17:26 ` Eric Blake
2017-07-26 22:19 ` Jeff Cody
2017-07-25 15:56 ` [Qemu-devel] [PATCH 2/2] iotests: Redirect stderr to stdout in 186 Max Reitz
2017-07-25 17:50 ` Eric Blake
2017-07-26 22:20 ` Jeff Cody
2017-07-27 12:24 ` 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=20170727122425.GC4767@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=eblake@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).