From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: lguest re-review
Date: Thu, 10 May 2007 11:30:32 +1000 [thread overview]
Message-ID: <1178760632.7286.187.camel@localhost.localdomain> (raw)
In-Reply-To: <20070509175018.a4a685b8.akpm@linux-foundation.org>
On Wed, 2007-05-09 at 17:50 -0700, Andrew Morton wrote:
> On Thu, 10 May 2007 10:24:08 +1000
> Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> > On Wed, 2007-05-09 at 02:51 -0700, Andrew Morton wrote:
> > > Some concern was expressed over the lguest review status, so I shall send
> > > the patches out again for people to review, to test, to make observations
> > > about the author's personal appearance, etc.
> >
> > Thanks Andrew,
> >
> > This means I can finally ack this patch (thanks Eric):
> >
> > From: ebiederm@xmission.com (Eric W. Biederman)
> > Subject: [PATCH] Revert "[PATCH] paravirt: Add startup infrastructure for paravirtualization"
> >
> > This reverts commit c9ccf30d77f04064fe5436027ab9d2230c7cdd94.
>
> I don't get it. Does lguest no longer need this code, or will
> it be reintroduced with an lguest merge, or something else?
Lguest no longer needs it (the magic signature patch you took).
HPA and Eric are brewing a new, shinier way for booting not-a-normal-pc
which will address lguest as well as others. But it seems they first
need to go through the "who knows most about ancient PCs" slapfight.
Thanks!
Rusty.
prev parent reply other threads:[~2007-05-10 1:30 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
2007-05-10 1:30 ` Rusty Russell [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=1178760632.7286.187.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.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).