public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Juan Quintela <quintela@redhat.com>,
	Glauber Costa <glommer@redhat.com>
Subject: Re: [PATCH 2/2] qemu-kvm: x86: Add support for VCPU event states
Date: Tue, 24 Nov 2009 16:15:42 +0200	[thread overview]
Message-ID: <4B0BEA8E.2090800@redhat.com> (raw)
In-Reply-To: <4B002349.5090309@redhat.com>

On 11/15/2009 05:50 PM, Avi Kivity wrote:
>
>>> Shouldn't you create 13 now?
>> No, I rather think Glauber's 12 should be downgraded to 11 - unless it
>> misses the qemu merge windows for 0.12. My extensions definitely target
>> that release, thus will likely carry 11 in upstream. And we should
>> really try to avoid diverging again.
>
> Agree.  Will commit the patches.

Ugh, so I did it the hard way by merging upstream and porting it 
(incorrectly), then going back to my queue to see that you had already 
nicely prepared this for me.

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


  reply	other threads:[~2009-11-24 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  0:04 [PATCH 1/2] qemu-kvm: x86: Refactor use of interrupt_bitmap Jan Kiszka
2009-11-12  0:05 ` [PATCH 2/2] qemu-kvm: x86: Add support for VCPU event states Jan Kiszka
2009-11-15 13:56   ` Avi Kivity
2009-11-15 14:21     ` Jan Kiszka
2009-11-15 14:27       ` Avi Kivity
2009-11-15 14:31         ` Jan Kiszka
2009-11-15 14:38           ` Avi Kivity
2009-11-15 15:02             ` Jan Kiszka
2009-11-15 15:10               ` Avi Kivity
2009-11-15 15:41                 ` Jan Kiszka
2009-11-15 15:50                   ` Avi Kivity
2009-11-24 14:15                     ` Avi Kivity [this message]
2009-11-24 22:08                   ` Marcelo Tosatti
2009-12-10 20:23                     ` Marcelo Tosatti

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=4B0BEA8E.2090800@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=quintela@redhat.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