From: Chris Wright <chrisw@osdl.org>
To: zach@vmware.com
Cc: akpm@osdl.org, chrisw@osdl.org, linux-kernel@vger.kernel.org,
virtualization@lists.osdl.org
Subject: Re: [PATCH 0/6] i386 virtualization patches, Set 3
Date: Tue, 16 Aug 2005 00:44:05 -0700 [thread overview]
Message-ID: <20050816074405.GZ7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <200508152258.j7FMw9p8005295@zach-dev.vmware.com>
* zach@vmware.com (zach@vmware.com) wrote:
> This patch set is based on 2.6.13-rc6 -mm1 broken out series. It applies
> and builds i386, x86_64, and um-i386 on 2.6.13-rc5. I've tested PAE and
> non-PAE SMP kernels and am working on an LDT test suite. Depends on
> the i386 cleanups, sub-arch movement, and LDT cleanups I've already sent
> out.
I put these in the virt-2.6 git tree, with the one minor wrprotect macro
change I mentioned.
thanks,
-chris
prev parent reply other threads:[~2005-08-16 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:58 [PATCH 0/6] i386 virtualization patches, Set 3 zach
2005-08-15 23:24 ` Andi Kleen
2005-08-15 23:27 ` David Lang
2005-08-15 23:35 ` Andi Kleen
2005-08-16 3:08 ` Brian Gerst
2005-08-16 3:33 ` Zachary Amsden
2005-08-16 7:44 ` Chris Wright [this message]
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=20050816074405.GZ7762@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox