From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
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 14:23:36 -0700 [thread overview]
Message-ID: <49E3AD58.2020700@goop.org> (raw)
In-Reply-To: <20090413203518.GC19972@elte.hu>
Ingo Molnar wrote:
> 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.
>
Yes, its just the core change without the /sys/hypervisor and
/dev/xen/evtchn drivers. The only difference is rebasing it off the
lazy mmu update preemption changes, which affected xen/mmu.c. The
required-features.h change is because 5f241e65 is not yet in mainline
(but probably should be).
J
next prev parent reply other threads:[~2009-04-13 21:23 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
2009-04-13 21:23 ` Jeremy Fitzhardinge [this message]
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=49E3AD58.2020700@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox