From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: virtualization@lists.osdl.org
Subject: Re: [PATCH] x86_64 paravirt_ops port
Date: Tue, 9 Jan 2007 09:14:23 -0200 [thread overview]
Message-ID: <20070109111423.GB5193@redhat.com> (raw)
In-Reply-To: <1168297540.19646.40.camel@localhost.localdomain>
> There's one critical bug which will stop it from booting reliably:
> > + Based on i386 work by Rusty Russel.
>
Thanks for the tip, Rusty. In fact, I fixed that, and the random crashes
disappeared. ;-)
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
next prev parent reply other threads:[~2007-01-09 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 14:08 [PATCH] x86_64 paravirt_ops port Glauber de Oliveira Costa
2007-01-08 23:05 ` Rusty Russell
2007-01-09 11:14 ` Glauber de Oliveira Costa [this message]
2007-01-09 1:00 ` Chris Wright
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=20070109111423.GB5193@redhat.com \
--to=gcosta@redhat.com \
--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).