From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: virtualization@lists.linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
lguest <lguest@ozlabs.org>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] lguest: paravirt boot code
Date: Tue, 23 Oct 2007 17:44:15 +1000 [thread overview]
Message-ID: <200710231744.16296.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200710230855.06253.borntraeger@de.ibm.com>
On Tuesday 23 October 2007 16:55:06 Christian Borntraeger wrote:
> Having virtio in Linus tree would make my life easier wiring it up for
> virtualization on s390.
Indeed. And given lguest's lack of interface guarantees, it make sense to use
it as the first virtio guinea pig. I expect changes as we adapt it for
others anyway.
> That reminds me that I promised Rusty to look at one small issue in virtio
> net driver. Nothing that should hold of the merge. I will sent the patch
> via Rusty when its ready.
Thanks,
Rusty.
next prev parent reply other threads:[~2007-10-23 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 2:37 [git pull] lguest: paravirt boot code Rusty Russell
2007-10-23 2:28 ` Linus Torvalds
2007-10-23 6:03 ` Rusty Russell
2007-10-23 6:03 ` Rusty Russell
2007-10-23 6:55 ` Christian Borntraeger
2007-10-23 7:44 ` Rusty Russell
2007-10-23 7:44 ` Rusty Russell [this message]
2007-10-23 6:55 ` Christian Borntraeger
2007-10-23 16:10 ` Linus Torvalds
2007-10-23 20:37 ` Jeff Garzik
2007-10-23 20:37 ` Jeff Garzik
2007-10-25 5:19 ` Rusty Russell
2007-10-25 5:19 ` Rusty Russell
2007-10-25 6:31 ` Stephen Rothwell
2007-10-25 6:31 ` Stephen Rothwell
2007-10-25 22:41 ` Linus Torvalds
2007-10-25 22:41 ` Linus Torvalds
2007-10-23 16:10 ` Linus Torvalds
2007-10-23 2:28 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 2:37 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=200710231744.16296.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=borntraeger@de.ibm.com \
--cc=hpa@zytor.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.