From: Juan Quintela <quintela@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qemu-iotests: Remove MIG_SOCKET from non-migration tests
Date: Wed, 23 May 2018 12:25:02 +0200 [thread overview]
Message-ID: <87sh6ibrep.fsf@secure.mitica> (raw)
In-Reply-To: <20180523095830.24362-3-kwolf@redhat.com> (Kevin Wolf's message of "Wed, 23 May 2018 11:58:30 +0200")
Kevin Wolf <kwolf@redhat.com> wrote:
> 185 and 191 define a MIG_SOCKET even though they don't do anything with
> migration. Remove the useless variable.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2018-05-23 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 9:58 [Qemu-devel] [PATCH 0/2] qemu-iotests: Add more tests to "migration" group Kevin Wolf
2018-05-23 9:58 ` [Qemu-devel] [PATCH 1/2] " Kevin Wolf
2018-05-23 10:23 ` Juan Quintela
2018-05-23 9:58 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: Remove MIG_SOCKET from non-migration tests Kevin Wolf
2018-05-23 10:25 ` Juan Quintela [this message]
2018-05-23 12:31 ` [Qemu-devel] [PATCH 0/2] qemu-iotests: Add more tests to "migration" group 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=87sh6ibrep.fsf@secure.mitica \
--to=quintela@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 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).