From: Gerd Hoffmann <kraxel@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: virtualization@lists.osdl.org
Subject: Re: [PATCH 0/5] paravirt clock source patches, #4
Date: Tue, 03 Jun 2008 15:46:21 +0200 [thread overview]
Message-ID: <48454B2D.5050406@redhat.com> (raw)
In-Reply-To: <48454A38.4090907@goop.org>
Jeremy Fitzhardinge 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.
>
> This all looks pretty good. How do you want this to get into the kernel?
>
> J
--
http://kraxel.fedorapeople.org/xenner/
next prev parent reply other threads:[~2008-06-03 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 13:07 [PATCH 0/5] paravirt clock source patches, #4 Gerd Hoffmann
2008-06-03 13:07 ` [PATCH 1/5] Add structs and functions for paravirt clocksource Gerd Hoffmann
2008-06-03 13:34 ` Jeremy Fitzhardinge
2008-06-03 13:07 ` [PATCH 2/5] Make xen use the paravirt clocksource structs and functions Gerd Hoffmann
2008-06-03 13:41 ` Jeremy Fitzhardinge
2008-06-03 13:07 ` [PATCH 3/5] Make kvm host use the paravirt clocksource structs Gerd Hoffmann
2008-06-03 13:07 ` [PATCH 4/5] Make kvm guest use the paravirt clocksource structs and functions Gerd Hoffmann
2008-06-03 13:07 ` [PATCH 5/5] Remove now unused structs from kvm_para.h Gerd Hoffmann
2008-06-03 13:26 ` David Miller
2008-06-03 13:42 ` [PATCH 0/5] paravirt clock source patches, #4 Jeremy Fitzhardinge
2008-06-03 13:46 ` Gerd Hoffmann [this message]
2008-06-03 13:49 ` Gerd Hoffmann
2008-06-04 14:01 ` Avi Kivity
2008-06-16 13:53 ` 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=48454B2D.5050406@redhat.com \
--to=kraxel@redhat.com \
--cc=jeremy@goop.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;
as well as URLs for NNTP newsgroup(s).