qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: New kvm-related qemu patch queue
Date: Sun, 10 Jan 2010 16:52:48 +0200	[thread overview]
Message-ID: <4B49E9C0.1020108@redhat.com> (raw)
In-Reply-To: <20100110144904.GO4905@redhat.com>

On 01/10/2010 04:49 PM, Gleb Natapov wrote:
>
>> If the feature is already in both, then morph qemu-kvm.git into what
>> is already in qemu.git.  Hopefully anything missing in qemu.git will
>> be discovered while making the changes.
>>
>>      
> What about bugs that are present only in qemu.git? Like this:
> http://patchwork.ozlabs.org/patch/42298/. Should it go through
> qemu-kvm.git/uq/master?
>    

Yes.  So there is a central place for kvm patches, and so they see autotest.


> What about this one: http://patchwork.ozlabs.org/patch/42447/ should it
> be postponed untill qemu.git and qemu-kvm.git converge on using the same
> cpuid infrastructure, or add similar functionality to qemu-kvm to,
> or add new cpu flags to qemu-kvm only and when cpuid code converge
> qemu.git will have it too?
>    

Best to make qemu-kvm.git and qemu.git converge first.  Duplicating the 
patch extends the problem.  Of course if something is urgent we can 
bypass the process.

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

  reply	other threads:[~2010-01-10 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 12:02 [Qemu-devel] New kvm-related qemu patch queue Avi Kivity
2010-01-10 14:28 ` [Qemu-devel] " Gleb Natapov
2010-01-10 14:30   ` Avi Kivity
2010-01-10 14:49     ` Gleb Natapov
2010-01-10 14:52       ` Avi Kivity [this message]
2010-01-11  7:51         ` Gleb Natapov
2010-01-11 15:30 ` Anthony Liguori
2010-01-17 12:51   ` Avi Kivity

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=4B49E9C0.1020108@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).