From: Markus Armbruster <armbru@redhat.com>
To: Michal Novotny <minovotn@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vl.c: Output error on invalid machine type provided
Date: Tue, 30 Jul 2013 17:17:08 +0200 [thread overview]
Message-ID: <87ppu06psb.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <ce2c57e3c0ffd169b943fefd7421930ad910ea0e.1375195925.git.minovotn@redhat.com> (Michal Novotny's message of "Tue, 30 Jul 2013 16:54:40 +0200")
Michal Novotny <minovotn@redhat.com> writes:
> Output error message when user provides the invalid machine type
> on the command line. This also saves time to find what issue is
> when you upgrade from one version of qemu to another version that
> doesn't support required machine type any longer.
Text from here
>
> The patch is checked using ./scripts/checkpatch.pl script and
> also is_help_option() function is being used.
>
> Michal
to here belongs below the '---' line, so it's ommitted from the commit
message.
>
> Signed-off-by: Michal Novotny <minovotn@redhat.com>
> ---
> vl.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/vl.c b/vl.c
> index 25b8f2f..563ae67 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -2671,6 +2671,11 @@ static QEMUMachine *machine_parse(const char *name)
> if (machine) {
> return machine;
> }
> +
> + if (name && !is_help_option(name)) {
> + printf("Error: Unsupported machine type '%s'\n", name);
> + }
> +
> printf("Supported machines are:\n");
> for (m = first_machine; m != NULL; m = m->next) {
> if (m->alias) {
next prev parent reply other threads:[~2013-07-30 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 14:54 [Qemu-devel] [PATCH v2] vl.c: Output error on invalid machine type provided Michal Novotny
2013-07-30 15:17 ` Markus Armbruster [this message]
2013-07-30 15:30 ` Michal Novotny
2013-07-30 19:05 ` Markus Armbruster
2013-07-30 19:10 ` Michal Novotny
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=87ppu06psb.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=minovotn@redhat.com \
--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.