From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [PATCH 0/5] paravirt clock source patches, #5
Date: Mon, 23 Jun 2008 08:06:12 -0400 [thread overview]
Message-ID: <485F91B4.6080300@goop.org> (raw)
In-Reply-To: <485F5A11.1000303@qumranet.com>
Avi Kivity wrote:
> Gerd Hoffmann wrote:
>> paravirt clock source patches, next round.
>>
>> There is now a pvclock-abi.h file with the structs and some longish
>> comments in it and everybody is switched over to use the stuff in
>> there.
>>
>> Some minor tweaks after super-fast review by Jeremy.
>>
>> The queue is on top of the kvm git tree. The first two patches should
>> have no kvm dependencies and should apply to linus tree just fine.
>>
>>
>
> Jeremy, can you ack the Xen bits for 2.6.26?
Hadn't I already?
Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
J
prev parent reply other threads:[~2008-06-23 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 14:17 [PATCH 0/5] paravirt clock source patches, #5 Gerd Hoffmann
2008-06-03 14:17 ` [PATCH 1/5] Add structs and functions for paravirt clocksource Gerd Hoffmann
2008-06-03 14:17 ` [PATCH 2/5] Make xen use the paravirt clocksource structs and functions Gerd Hoffmann
2008-06-03 14:17 ` [PATCH 3/5] Make kvm host use the paravirt clocksource structs Gerd Hoffmann
2008-06-03 14:17 ` [PATCH 4/5] Make kvm guest use the paravirt clocksource structs and functions Gerd Hoffmann
2008-06-03 14:17 ` [PATCH 5/5] Remove now unused structs from kvm_para.h Gerd Hoffmann
2008-06-23 8:08 ` [PATCH 0/5] paravirt clock source patches, #5 Avi Kivity
2008-06-23 12:06 ` Jeremy Fitzhardinge [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=485F91B4.6080300@goop.org \
--to=jeremy@goop.org \
--cc=avi@qumranet.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=virtualization@lists.osdl.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