All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Breakage due to commit c1699988 ("v3: don't call reset functions on cpu initialization")
Date: Sun, 22 Nov 2009 16:42:12 +0200	[thread overview]
Message-ID: <4B094DC4.1000107@redhat.com> (raw)

A qemu-kvm which merges this commit breaks badly (see qemu-kvm.git next 
branch).  In the commit log for this commit, you write

     I tested it with qemu (with and without io-thread) and qemu-kvm, and it
     seems to be doing okay - although qemu-kvm uses a slightly 
different patch.

Can you share the slightly different patch (against 'next') please?

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


             reply	other threads:[~2009-11-22 14:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 14:42 Avi Kivity [this message]
2009-11-23 19:00 ` Breakage due to commit c1699988 ("v3: don't call reset functions on cpu initialization") Glauber Costa
2009-11-23 21:07   ` Glauber Costa
2009-11-24 10:01     ` Avi Kivity
2009-11-24 12:16       ` Glauber Costa
2009-11-24 12:50         ` Avi Kivity
2009-11-24 10:00   ` 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=4B094DC4.1000107@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.