From: Wang Xin <wangxinxin.wang@huawei.com>
To: qemu-devel@nongnu.org, mst@redhat.com
Cc: ehabkost@redhat.com, arei.gonglei@huawei.com,
Wang Xin <wangxinxin.wang@huawei.com>
Subject: [Qemu-devel] [PATCH] pc: correct misspelled CPU model-id for pc 2.2
Date: Wed, 31 Jan 2018 11:01:08 +0800 [thread overview]
Message-ID: <1517367668-25048-1-git-send-email-wangxinxin.wang@huawei.com> (raw)
Signed-off-by: Wang Xin <wangxinxin.wang@huawei.com>
diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
index bb49165..635c8b2 100644
--- a/include/hw/i386/pc.h
+++ b/include/hw/i386/pc.h
@@ -617,7 +617,7 @@ bool e820_get_entry(int, uint32_t, uint64_t *, uint64_t *);
#define PC_COMPAT_2_2 \
HW_COMPAT_2_2 \
- PC_CPU_MODEL_IDS("2.3.0") \
+ PC_CPU_MODEL_IDS("2.2.0") \
{\
.driver = "kvm64" "-" TYPE_X86_CPU,\
.property = "vme",\
--
2.8.1.windows.1
next reply other threads:[~2018-01-31 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 3:01 Wang Xin [this message]
2018-01-31 14:01 ` [Qemu-devel] [PATCH] pc: correct misspelled CPU model-id for pc 2.2 Michael S. Tsirkin
2018-01-31 14:38 ` Eduardo Habkost
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=1517367668-25048-1-git-send-email-wangxinxin.wang@huawei.com \
--to=wangxinxin.wang@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=ehabkost@redhat.com \
--cc=mst@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).