qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	"Don Slutz" <Don@cloudswitch.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] target-i386: cpu: recover items 28-31 of ext2_feature_name
Date: Mon, 29 Oct 2012 15:34:55 +0100	[thread overview]
Message-ID: <20121029143455.GA16480@ohm.aurel32.net> (raw)
In-Reply-To: <1351087833-25772-1-git-send-email-ehabkost@redhat.com>

On Wed, Oct 24, 2012 at 12:10:33PM -0200, Eduardo Habkost wrote:
> I removed a line by mistake on commit
> 3b671a40cab2404bc63e57db8cd3afa4ec70bfab, containing the flags lm/i64,
> 3dnow, and 3dnowext. This patch restores the removed line.
> 
> Reported-by: Don Slutz <Don@cloudswitch.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
>  target-i386/cpu.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index f3708e6..6411042 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -74,6 +74,7 @@ static const char *ext2_feature_name[] = {
>      NULL /* pat */, NULL /* pse36 */, NULL, NULL /* Linux mp */,
>      "nx|xd", NULL, "mmxext", NULL /* mmx */,
>      NULL /* fxsr */, "fxsr_opt|ffxsr", "pdpe1gb" /* AMD Page1GB */, "rdtscp",
> +    NULL, "lm|i64", "3dnowext", "3dnow",
>  };
>  static const char *ext3_feature_name[] = {
>      "lahf_lm" /* AMD LahfSahf */, "cmp_legacy", "svm", "extapic" /* AMD ExtApicSpace */,

Thanks, applied.


-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2012-10-29 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 14:10 [Qemu-devel] [PATCH] target-i386: cpu: recover items 28-31 of ext2_feature_name Eduardo Habkost
2012-10-24 16:34 ` Don Slutz
2012-10-29 14:34 ` Aurelien Jarno [this message]

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=20121029143455.GA16480@ohm.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=Don@cloudswitch.com \
    --cc=afaerber@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@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).