All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 2/2] qemu-iotests: Remove MIG_SOCKET from non-migration tests
Date: Wed, 23 May 2018 11:58:30 +0200	[thread overview]
Message-ID: <20180523095830.24362-3-kwolf@redhat.com> (raw)
In-Reply-To: <20180523095830.24362-1-kwolf@redhat.com>

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>
---
 tests/qemu-iotests/185 | 2 --
 tests/qemu-iotests/191 | 2 --
 2 files changed, 4 deletions(-)

diff --git a/tests/qemu-iotests/185 b/tests/qemu-iotests/185
index 9a2d317414..deb42cc886 100755
--- a/tests/qemu-iotests/185
+++ b/tests/qemu-iotests/185
@@ -27,8 +27,6 @@ echo "QA output created by $seq"
 here=`pwd`
 status=1 # failure is the default!
 
-MIG_SOCKET="${TEST_DIR}/migrate"
-
 _cleanup()
 {
     rm -f "${TEST_IMG}.mid"
diff --git a/tests/qemu-iotests/191 b/tests/qemu-iotests/191
index dfad6555e4..77224eb151 100755
--- a/tests/qemu-iotests/191
+++ b/tests/qemu-iotests/191
@@ -27,8 +27,6 @@ echo "QA output created by $seq"
 here=`pwd`
 status=1 # failure is the default!
 
-MIG_SOCKET="${TEST_DIR}/migrate"
-
 _cleanup()
 {
     rm -f "${TEST_IMG}.mid"
-- 
2.13.6

  parent reply	other threads:[~2018-05-23  9:58 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 ` Kevin Wolf [this message]
2018-05-23 10:25   ` [Qemu-devel] [PATCH 2/2] qemu-iotests: Remove MIG_SOCKET from non-migration tests Juan Quintela
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=20180523095830.24362-3-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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.