From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
Laurent Vivier <laurent@vivier.eu>,
Cleber Rosa <crosa@redhat.com>
Subject: [PATCH 1/2] analyze-migration.py: fix a long standing typo
Date: Fri, 15 Oct 2021 15:16:44 +0200 [thread overview]
Message-ID: <20211015131645.501281-2-lvivier@redhat.com> (raw)
In-Reply-To: <20211015131645.501281-1-lvivier@redhat.com>
The parameters of '-d' can be either 'state' or 'desc', not 'dump'
as it is reported in the error message.
Fixes: b17425701d66 ("Add migration stream analyzation script")
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
---
scripts/analyze-migration.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/analyze-migration.py b/scripts/analyze-migration.py
index d7177b212c86..9d239d309f33 100755
--- a/scripts/analyze-migration.py
+++ b/scripts/analyze-migration.py
@@ -610,4 +610,4 @@ def default(self, o):
dump.read(desc_only = True)
print(jsonenc.encode(dump.vmsd_desc))
else:
- raise Exception("Please specify either -x, -d state or -d dump")
+ raise Exception("Please specify either -x, -d state or -d desc")
--
2.31.1
next prev parent reply other threads:[~2021-10-15 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 13:16 [PATCH 0/2] analyze-migration.py: trivial fixes Laurent Vivier
2021-10-15 13:16 ` Laurent Vivier [this message]
2021-10-15 13:24 ` [PATCH 1/2] analyze-migration.py: fix a long standing typo Philippe Mathieu-Daudé
2021-10-15 13:16 ` [PATCH 2/2] analyze-migration.py: fix extract contents ('-x') errors Laurent Vivier
2021-10-15 14:21 ` Philippe Mathieu-Daudé
2021-10-19 7:56 ` [PATCH 0/2] analyze-migration.py: trivial fixes Laurent Vivier
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=20211015131645.501281-2-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).