From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
yan@daynix.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] console class in kvm
Date: Mon, 26 Mar 2012 15:43:31 +0200 [thread overview]
Message-ID: <4F707283.1070501@redhat.com> (raw)
In-Reply-To: <20120326133717.GC16511@redhat.com>
On 03/26/2012 03:37 PM, Michael S. Tsirkin wrote:
> Exactly. qemu-kvm used to set the class to CLASS_OTHER while
> the current code sets it to PCI_CLASS_COMMUNICATION_OTHER.
> Do we want support for CLASS_OTHER or is it ok to drop it?
>
>
Looks like starting with qemu-kvm-0.11, qemu-kvm matches qemu. I think
we can let the compatibility problem with qemu-kvm-0.10 remain.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-26 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 9:48 [Qemu-devel] console class in kvm Michael S. Tsirkin
2012-03-26 10:18 ` Avi Kivity
2012-03-26 11:19 ` Michael S. Tsirkin
2012-03-26 12:29 ` Avi Kivity
2012-03-26 13:37 ` Michael S. Tsirkin
2012-03-26 13:43 ` Avi Kivity [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=4F707283.1070501@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yan@daynix.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).