From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] Start using KVMState
Date: Thu, 18 Jun 2009 12:15:12 +0300 [thread overview]
Message-ID: <4A3A05A0.2070504@redhat.com> (raw)
In-Reply-To: <1244488224-31171-1-git-send-email-glommer@redhat.com>
On 06/08/2009 10:10 PM, Glauber Costa wrote:
> Guys,
>
> This is to address the feedback I received in the last attempt.
>
Does this fix the tpr patching regression? What was the problem?
It always helps to explicitly list changes and add a version number to
patchsets, to help maintainers with limited memory capacity.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-18 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 19:10 [PATCH 0/4] Start using KVMState Glauber Costa
2009-06-08 19:10 ` [PATCH 1/4] get rid of libkvm-common.h Glauber Costa
2009-06-08 19:10 ` [PATCH 2/4] pull qemu headers into libkvm Glauber Costa
2009-06-08 19:10 ` [PATCH 3/4] Move KVMState to common header Glauber Costa
2009-06-08 19:10 ` [PATCH 4/4] Use KVMState as main state container Glauber Costa
2009-06-08 19:54 ` [PATCH 3/4] Move KVMState to common header Jan Kiszka
2009-06-08 20:14 ` Glauber Costa
2009-06-08 22:01 ` Anthony Liguori
2009-06-18 9:15 ` Avi Kivity [this message]
2009-06-18 13:29 ` [PATCH 0/4] Start using KVMState Glauber Costa
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=4A3A05A0.2070504@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.