From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm@vger.kernel.org, aliguori@codemonkey.ws, mtosatti@redhat.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/2] Paravirt loops per jiffy
Date: Tue, 29 Jul 2008 17:17:57 +0300 [thread overview]
Message-ID: <488F2695.4080501@qumranet.com> (raw)
In-Reply-To: <1217256473-10222-1-git-send-email-gcosta@redhat.com>
Glauber Costa wrote:
> Resending, as avi seem to have missed the patches.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-07-29 14:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 16:15 [PATCH 0/2] Paravirt loops per jiffy calculation Glauber Costa
2008-07-22 16:15 ` [PATCH 1/2] factor out cpu_khz to common code Glauber Costa
2008-07-22 16:15 ` Glauber Costa
2008-07-22 16:15 ` [PATCH 2/2] use paravirt function to calculate cpu khz Glauber Costa
2008-07-22 16:15 ` Glauber Costa
2008-07-23 10:07 ` [PATCH 0/2] Paravirt loops per jiffy calculation Gerd Hoffmann
2008-07-23 10:07 ` Gerd Hoffmann
2008-07-23 13:35 ` Glauber Costa
2008-07-23 13:35 ` Glauber Costa
2008-07-27 7:59 ` Avi Kivity
2008-07-27 7:59 ` Avi Kivity
2008-07-28 14:47 ` [PATCH 0/2] Paravirt loops per jiffy Glauber Costa
2008-07-28 14:47 ` Glauber Costa
2008-07-28 14:47 ` [PATCH 1/2] factor out cpu_khz to common code Glauber Costa
2008-07-28 14:47 ` Glauber Costa
2008-07-28 14:47 ` [PATCH 2/2] use paravirt function to calculate cpu khz Glauber Costa
2008-07-28 14:47 ` Glauber Costa
2008-07-29 14:17 ` [PATCH 0/2] Paravirt loops per jiffy Avi Kivity
2008-07-29 14:17 ` Avi Kivity [this message]
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=488F2695.4080501@qumranet.com \
--to=avi@qumranet.com \
--cc=aliguori@codemonkey.ws \
--cc=gcosta@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=virtualization@lists.linux-foundation.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.