All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt_ops queue rebased
Date: Sun, 6 May 2007 23:49:40 +0200	[thread overview]
Message-ID: <200705062349.40343.ak@suse.de> (raw)
In-Reply-To: <463E0E8D.3050806@goop.org>

On Sunday 06 May 2007 19:21:17 Jeremy Fitzhardinge wrote:
> 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

There were problems with my patch and yours dependend on it so I deferred both.

> or the paravirt patch?  Should I resubmit the 
> paravirt-sched_clock patch based on git?

Not needed, I still have it.
 
> 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?

Only a few patches left, like unwinder, vDSO, sched-clock. 

-Andi

      parent reply	other threads:[~2007-05-06 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06 17:21 paravirt_ops queue rebased Jeremy Fitzhardinge
2007-05-06 18:12 ` 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 [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=200705062349.40343.ak@suse.de \
    --to=ak@suse.de \
    --cc=James.Bottomley@hansenpartnership.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 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.