From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Xiao Guangrong <xiaoguangrong@tencent.com>,
Babu Moger <babu.moger@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] pc: Remove PC_COMPAT_2_12 from 3.0 machine-types
Date: Mon, 11 Jun 2018 10:51:07 +0800 [thread overview]
Message-ID: <0fd10e24-1890-e8a0-0628-df6707d0f25a@gmail.com> (raw)
In-Reply-To: <20180608192940.19548-1-ehabkost@redhat.com>
On 06/09/2018 03:29 AM, Eduardo Habkost wrote:
> commit f548222c added PC_COMPAT_2_12 to the 3.0 PC machine-types.
> I believe this happened during manual conflict resolution when
> applying the patch.
>
Indeed!
Reviewed-by: Xiao Guangrong <xiaoguangrong@tencent.com>
prev parent reply other threads:[~2018-06-11 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 19:29 [Qemu-devel] [PATCH] pc: Remove PC_COMPAT_2_12 from 3.0 machine-types Eduardo Habkost
2018-06-10 12:27 ` Marcel Apfelbaum
2018-06-11 2:51 ` Xiao Guangrong [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=0fd10e24-1890-e8a0-0628-df6707d0f25a@gmail.com \
--to=guangrong.xiao@gmail.com \
--cc=babu.moger@amd.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=xiaoguangrong@tencent.com \
/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).