From: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Wright <chrisw@sous-sol.org>, virtualization@lists.osdl.org
Subject: Re: [PATCH] Fix CONFIG_PARAVIRT for 2.6.19-rc5-mm1
Date: 9 Nov 2006 15:11:09 +0100
Date: Thu, 9 Nov 2006 15:11:09 +0100 [thread overview]
Message-ID: <20061109141109.GA63791@muc.de> (raw)
In-Reply-To: <20061109000939.7a48851f.akpm@osdl.org>
On Thu, Nov 09, 2006 at 12:09:39AM -0800, Andrew Morton wrote:
> On Wed, 8 Nov 2006 23:39:04 -0800
> Andrew Morton <akpm@osdl.org> wrote:
>
> > > Can you please resend the patchkit with these patches included?
> > >
> > > (and any further changes folded in into the respective patches)
> > >
> >
> > argh.
> >
> > I'll do it.
>
> OK, all done.
>
> I kept prep-for-paravirt-be-careful-about-touching-bios.patch (below)
> separate, because it's dependent on
> x86_64-mm-i386-create-e820.c-to-handle-standard-io-mem-resources.patch. It
> could be folded into one of the other patches I guess.
>
> So I have:
>
> paravirt-i386-header-and-stubs-for-paravirtualisation.patch
> paravirt-i386-patch-inline-replacements-for.patch
> paravirt-i386-more-generic-paravirtualization.patch
> paravirt-i386-allow-selected-bug-checks-to-be.patch
> paravirt-i386-allow-disabling-legacy-power.patch
> paravirt-i386-add-apic-accessors-to-paravirt-ops.patch
> paravirt-i386-add-mmu-virtualization-to.patch
> prep-for-paravirt-be-careful-about-touching-bios.patch
Thanks. Where can I get them?
-Andi
next prev parent reply other threads:[~2006-11-09 14:11 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
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 [this message]
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=20061109141109.GA63791@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.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 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).