From: Eduardo Habkost <ehabkost@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL v2 3/3] target-i386: Reject invalid CPU feature names on the command-line
Date: Thu, 4 Sep 2014 15:17:33 -0300 [thread overview]
Message-ID: <20140904181733.GE32084@thinpad.lan.raisama.net> (raw)
In-Reply-To: <1409851213-14330-4-git-send-email-afaerber@suse.de>
On Thu, Sep 04, 2014 at 07:20:13PM +0200, Andreas Färber wrote:
[...]
> +static uint32_t x86_cpu_get_supported_feature_word(FeatureWord w,
> + bool migratable_only);
> +
> #ifdef CONFIG_KVM
>
> static int cpu_x86_fill_model_id(char *str)
> @@ -1310,9 +1314,6 @@ static void host_x86_cpu_class_init(ObjectClass *oc, void *data)
> dc->props = host_x86_cpu_properties;
> }
>
> -static uint32_t x86_cpu_get_supported_feature_word(FeatureWord w,
> - bool migratable_only);
> -
This was supposed to be squashed into patch 1/2, not this one.
(That was my fault, as I mentioned the wrong patch when I submitted the
build error fix.)
--
Eduardo
next prev parent reply other threads:[~2014-09-04 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 17:20 [Qemu-devel] [PULL 0/3] QOM CPUState patch queue 2014-09-04 Andreas Färber
2014-09-04 17:20 ` [Qemu-devel] [PULL v2 1/3] exec: Save CPUState::exception_index field Andreas Färber
2014-09-04 22:50 ` Peter Maydell
2014-09-05 12:16 ` Andreas Färber
2014-09-04 17:20 ` [Qemu-devel] [PULL v2 2/3] target-i386: Support migratable=no properly Andreas Färber
2014-09-04 17:20 ` [Qemu-devel] [PULL v2 3/3] target-i386: Reject invalid CPU feature names on the command-line Andreas Färber
2014-09-04 18:17 ` Eduardo Habkost [this message]
2014-09-04 18:40 ` [Qemu-devel] [PULL 0/3] QOM CPUState patch queue 2014-09-04 Peter Maydell
2014-09-05 14:45 ` Andreas Färber
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=20140904181733.GE32084@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--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.