From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>, "H. Peter Anvin" <hpa@zytor.com>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen: fix 32-bit build resulting from mmu move
Date: Tue, 3 Feb 2009 13:21:12 +0100 [thread overview]
Message-ID: <20090203122112.GD19979@elte.hu> (raw)
In-Reply-To: <49876C6E.3010809@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Moving the mmu code from enlighten.c to mmu.c inadvertently broke the
> 32-bit build. Fix it.
>
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> ---
> arch/x86/xen/mmu.c | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
that goes on top of the recent tip/x86/paravirt changes, right? No
objections, i'm wondering why my testing didnt find any build breakage.
Could you send me a .config that triggers the breakage?
Ingo
next prev parent reply other threads:[~2009-02-03 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:58 [PATCH] xen: fix 32-bit build resulting from mmu move Jeremy Fitzhardinge
2009-02-03 12:21 ` Ingo Molnar [this message]
2009-02-03 17:14 ` Jeremy Fitzhardinge
2009-02-03 17:14 ` Jeremy Fitzhardinge
2009-02-03 17:36 ` Ingo Molnar
2009-02-03 17:36 ` Ingo Molnar
2009-02-03 18:05 ` Jeremy Fitzhardinge
2009-02-03 18:05 ` Jeremy Fitzhardinge
2009-02-03 18:14 ` Ingo Molnar
2009-02-03 18:14 ` Ingo Molnar
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=20090203122112.GD19979@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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.