qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Justin >> \"Justin M. Forbes\"" <jmforbes@linuxtx.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 1.0] pc_piix: set qxl revision to 2 for pc-0.14
Date: Mon, 14 Nov 2011 19:51:25 +0200	[thread overview]
Message-ID: <4EC1551D.1020803@redhat.com> (raw)
In-Reply-To: <4EC1546E.3080004@codemonkey.ws>

On 11/14/2011 07:48 PM, Anthony Liguori wrote:
> On 11/14/2011 11:45 AM, Avi Kivity wrote:
>> On 11/14/2011 06:07 PM, Anthony Liguori wrote:
>>>> Antony, can you apply this directly or do you wanna have a
>>>> single-patch-pull-request instead?
>>>
>>>
>>> Yes, I'll apply directly.
>>
>> Does stable-0.15 need it too?
>
> You mean to set the revision to 2 for 0.14, right?  Not to set the
> revision to 2 for 0.15?
>

I mean, change stable-0.15 so that if it is invoked with -M 0.14, you
get a rev 2 qxl device.

The Fedora 16 regression which triggered this was running 0.15, I
imagine (but it could be running virt-preview, or something, so not sure).

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2011-11-14 17:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13 13:27 [Qemu-devel] [RFC 1.0] pc_piix: set qxl revision to 2 for pc-0.14 Alon Levy
2011-11-14 10:40 ` Gerd Hoffmann
2011-11-14 11:44   ` Alon Levy
2011-11-14 15:55     ` Gerd Hoffmann
2011-11-14 16:07       ` Anthony Liguori
2011-11-14 17:45         ` Avi Kivity
2011-11-14 17:48           ` Anthony Liguori
2011-11-14 17:51             ` Avi Kivity [this message]
2011-11-15 10:54               ` Gerd Hoffmann
2011-11-15 15:04 ` Anthony Liguori

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=4EC1551D.1020803@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=jmforbes@linuxtx.org \
    --cc=kraxel@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).