From: Andrew Morton <akpm@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
virtualization <virtualization@lists.osdl.org>
Subject: Re: [PATCH] Fix CONFIG_PARAVIRT for 2.6.19-rc5-mm1
Date: Wed, 8 Nov 2006 17:20:14 -0800 [thread overview]
Message-ID: <20061108172014.b4bcea17.akpm@osdl.org> (raw)
In-Reply-To: <1163034102.15681.6.camel@localhost.localdomain>
On Thu, 09 Nov 2006 12:01:42 +1100
Rusty Russell <rusty@rustcorp.com.au> wrote:
> OK, at least two patches got dropped on the way from the mm tree to
> Andi's tree: the desc.h cleanup, and the processor.h rearrangement.
> Merging into Andi's tree without these patches must have been a
> nightmare 8(
>
> Andi then tried to fix it with x86_64-mm-paravirt-compile.patch but then
> it didn't boot so he disabled it in x86_64-mm-paravirt-broken.patch
>
> This patch undoes those two patches and rearranges processor.h correctly
> so the kernel compiles and boots with CONFIG_PARAVIRT. Andi's
> "paravirt-compile" patch also cleans up the spinlock header, which is
> good but should probably be patched separately.
Fun. Andi, I have a mountain of fixes against your tree. Whatever you
do, don't change anything! I'll get it all sent over later today.
next prev parent reply other threads:[~2006-11-09 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 1:01 [PATCH] Fix CONFIG_PARAVIRT for 2.6.19-rc5-mm1 Rusty Russell
2006-11-09 1:20 ` Andrew Morton [this message]
2006-11-09 7:31 ` Andi Kleen
2006-11-09 7:50 ` Andrew Morton
2006-11-09 7:12 ` Andi Kleen
2006-11-09 7:39 ` Andrew Morton
2006-11-09 8:09 ` Andrew Morton
2006-11-09 14:11 ` Andi Kleen
2006-11-09 17:13 ` Andrew Morton
2006-11-09 17:14 ` Andrew Morton
2006-11-11 4:34 ` Rusty Russell
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=20061108172014.b4bcea17.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@muc.de \
--cc=chrisw@sous-sol.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).