virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt repo rebased to 2.6.21-rc6-mm1
Date: Tue, 10 Apr 2007 16:29:44 -0700	[thread overview]
Message-ID: <461C1DE8.8030307@vmware.com> (raw)
In-Reply-To: <461C1C7B.5080509@goop.org>

Jeremy Fitzhardinge wrote:
> Seems to work OK for native and Xen.  I had to play a bit with the
> paravirt-sched-clock patch to deal with the VMI changes.  Zach, can you
> check that it still works?
>
> Thanks,
>   

Thanks, btw.

Zach

  parent reply	other threads:[~2007-04-10 23:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 23:23 paravirt repo rebased to 2.6.21-rc6-mm1 Jeremy Fitzhardinge
2007-04-10 23:29 ` Zachary Amsden
2007-04-11  0:10   ` Chris Wright
2007-04-10 23:29 ` Zachary Amsden [this message]
2007-04-10 23:48 ` Chris Wright
2007-04-12  8:54 ` Chris Wright
2007-04-12 15:40   ` Zachary Amsden

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=461C1DE8.8030307@vmware.com \
    --to=zach@vmware.com \
    --cc=chrisw@sous-sol.org \
    --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).