From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 3/3] iotests: Allow 147 to be run concurrently
Date: Wed, 23 Jan 2019 18:34:13 +0100 [thread overview]
Message-ID: <8204d711-5769-c2f7-7baf-0d26eaf8fa54@redhat.com> (raw)
In-Reply-To: <04d2a9e7-9cb8-74cf-0c0e-0c9d19940020@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 415 bytes --]
On 23.01.19 14:05, Max Reitz wrote:
> On 21.01.19 21:50, John Snow wrote:
[...]
>> I guess my only other observation is that we have a lot of "while True"
>> loops now, is it worth creating some kind of helper that does the dirty
>> work of finding a serviceable port or nah?
>
> Seems reasonable, I'll see how it looks.
If I do that, the diff stat looks to be 40+, 33-. Is that worth it?
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-23 17:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 23:47 [Qemu-devel] [PATCH 0/3] iotests: Allow 147 to be run concurrently Max Reitz
2018-12-21 23:47 ` [Qemu-devel] [PATCH 1/3] iotests.py: Add qemu_nbd_pipe() Max Reitz
2019-01-21 20:55 ` Eric Blake
2019-01-23 13:06 ` Max Reitz
2019-01-23 14:27 ` Eric Blake
2018-12-21 23:47 ` [Qemu-devel] [PATCH 2/3] iotests: Bind qemu-nbd to localhost in 147 Max Reitz
2019-01-21 20:56 ` Eric Blake
2018-12-21 23:47 ` [Qemu-devel] [PATCH 3/3] iotests: Allow 147 to be run concurrently Max Reitz
2019-01-21 20:50 ` [Qemu-devel] [Qemu-block] " John Snow
2019-01-23 13:05 ` Max Reitz
2019-01-23 17:34 ` Max Reitz [this message]
2019-01-23 17:47 ` John Snow
2019-01-25 15:01 ` Max Reitz
2019-01-21 21:02 ` [Qemu-devel] " Eric Blake
2019-01-23 13:12 ` Max Reitz
2019-01-23 14:33 ` Eric Blake
2019-01-23 14:37 ` Max Reitz
2019-01-23 14:43 ` Daniel P. Berrangé
2019-01-31 1:01 ` [Qemu-devel] [PATCH 0/3] " Max Reitz
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=8204d711-5769-c2f7-7baf-0d26eaf8fa54@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.