From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: paravirt_ops queue rebased
Date: Sun, 06 May 2007 10:21:17 -0700 [thread overview]
Message-ID: <463E0E8D.3050806@goop.org> (raw)
I just rebased my paravirt_ops patch queue to current git. Looks like
almost all the pre-req patches are now in, which is nice.
The only missing thing from your patches was you sched_clock patches and
the sched_clock paravirt-op. Are there still problems with either your
sched_clock patch or the paravirt patch? Should I resubmit the
paravirt-sched_clock patch based on git?
The only other general patches before the Xen series I have left in my
queue are:
i386-common-smp.patch
i386-fix-voyager-build.patch
vsyscall-note-use-elfnote_h.patch
I obviously don't depend the voyager patch, but I tweaked it a bit to
apply to the current git tree.
How is your patch queue looking now? Is there much left?
J
next reply other threads:[~2007-05-06 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 17:21 Jeremy Fitzhardinge [this message]
2007-05-06 18:12 ` paravirt_ops queue rebased James Bottomley
2007-05-06 23:27 ` Jeremy Fitzhardinge
[not found] ` <1178558797.3729.21.camel@mulgrave.il.steeleye.com>
2007-05-07 18:14 ` Jeremy Fitzhardinge
2007-05-06 21:49 ` Andi Kleen
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=463E0E8D.3050806@goop.org \
--to=jeremy@goop.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ak@suse.de \
--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 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.