From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] iotests: 147: Don't test inet6 if not available
Date: Wed, 17 May 2017 13:59:32 +0200 [thread overview]
Message-ID: <20170517115932.GC4856@noname.redhat.com> (raw)
In-Reply-To: <20170517021302.GF27669@lemon.lan>
Am 17.05.2017 um 04:13 hat Fam Zheng geschrieben:
> On Fri, 05/05 18:21, Fam Zheng wrote:
> > This is the case in our docker tests, as we use --net=none there. Skip
> > this method.
>
> Ping. Is this patch okay?
I thought you might want to respond to Dan's comment. If you don't plan
to make the change he suggests, let me know and I'll queue the patch as
it is.
Kevin
next prev parent reply other threads:[~2017-05-17 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 10:21 [Qemu-devel] [PATCH] iotests: 147: Don't test inet6 if not available Fam Zheng
2017-05-05 10:41 ` Daniel P. Berrange
2017-05-17 12:21 ` Fam Zheng
2017-05-17 2:13 ` Fam Zheng
2017-05-17 11:59 ` Kevin Wolf [this message]
2017-05-17 12:10 ` Fam Zheng
2017-05-17 12:15 ` Daniel P. Berrange
2017-05-17 12:27 ` Kevin Wolf
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=20170517115932.GC4856@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=famz@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).