From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>
Subject: Re: lguest re-review
Date: Wed, 09 May 2007 19:22:32 -0600 [thread overview]
Message-ID: <m1wszhsc9z.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070509175018.a4a685b8.akpm@linux-foundation.org> (Andrew Morton's message of "Wed, 9 May 2007 17:50:18 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> I don't get it. Does lguest no longer need this code, or will
> it be reintroduced with an lguest merge, or something else?
No longer needed.
For the short term lguest has a separate entry point. For the long term
2.6.23 we will rev the boot protocol, so lguest and Xen can work with
a bzImage and use our standard set of kernel parameters.
Eric
next prev parent reply other threads:[~2007-05-10 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 9:51 lguest re-review Andrew Morton
2007-05-10 0:24 ` Rusty Russell
2007-05-10 0:50 ` Andrew Morton
2007-05-10 1:22 ` Eric W. Biederman [this message]
2007-05-10 1:30 ` 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=m1wszhsc9z.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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).