All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Xen bugfixes for -rc1
Date: Mon, 13 Apr 2009 22:35:18 +0200	[thread overview]
Message-ID: <20090413203518.GC19972@elte.hu> (raw)
In-Reply-To: <49E385FE.8050902@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Hi Linus,
>
> Please pull this set of Xen bugfixes/cleanups for -rc[12].
>
> Thanks,
>    J
>
> The following changes since commit 577c9c456f0e1371cbade38eaf91ae8e8a308555:
>  Linus Torvalds (1):
>        Linux 2.6.30-rc1
>
> are available in the git repository at:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git for-rc1/xen/core

I've pulled it into x86/urgent as well, thanks.

This is a strict subset of the Xen tree i sent to Linus to earlier, 
right?

The two places where there seems to have been some rebasing 
complexity is arch/x86/include/asm/required-features.h and 
arch/x86/xen/mmu.c.

Those bits are tested now so while i have not tested this specific 
rebased/narrowed variant yet, Linus please feel free to pull it:

  Acked-by: Ingo Molnar <mingo@elte.hu>

as these fixes have been delayed enough already. Or if not, i'll 
send these bits tomorrow via x86/urgent, after testing.

	Ingo

  reply	other threads:[~2009-04-13 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 18:35 [GIT PULL] Xen bugfixes for -rc1 Jeremy Fitzhardinge
2009-04-13 20:35 ` Ingo Molnar [this message]
2009-04-13 21:23   ` Jeremy Fitzhardinge
2009-04-13 21:30   ` Jeremy Fitzhardinge

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=20090413203518.GC19972@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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.