From: Stefan Hajnoczi <stefanha@gmail.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Jiri Denemark <jdenemar@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix '-cpu ?' Segfault
Date: Wed, 21 Mar 2012 13:24:43 +0000 [thread overview]
Message-ID: <20120321132443.GA27175@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1332333220-31420-1-git-send-email-ehabkost@redhat.com>
On Wed, Mar 21, 2012 at 09:33:40AM -0300, Eduardo Habkost wrote:
> Fix stupid copy&paste mistake at commit
> ecf40beae7dcbb057d4f115207f9d8276832a774: I moved code around but kept
> "optarg" on the cpu_list() call.
>
> Reported-by: Jiri Denemark <jdenemar@redhat.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> vl.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks, applied to the trivial patches tree:
https://github.com/stefanha/qemu/commits/trivial-patches
Stefan
next prev parent reply other threads:[~2012-03-21 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:33 [Qemu-devel] [PATCH] fix '-cpu ?' Segfault Eduardo Habkost
2012-03-21 13:24 ` Stefan Hajnoczi [this message]
2012-03-22 13:28 ` Stefan Berger
2012-03-22 13:46 ` Andreas Färber
2012-03-22 14:05 ` Eduardo Habkost
2012-03-23 20:31 ` Michael Roth
2012-03-23 20:37 ` Alon Levy
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=20120321132443.GA27175@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=ehabkost@redhat.com \
--cc=jdenemar@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 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).