From: Christian Borntraeger <borntraeger@de.ibm.com>
To: virtualization@lists.linux-foundation.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
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 08:55:06 +0200 [thread overview]
Message-ID: <200710230855.06253.borntraeger@de.ibm.com> (raw)
In-Reply-To: <200710231603.21620.rusty@rustcorp.com.au>
Am Dienstag, 23. Oktober 2007 schrieb Rusty Russell:
> git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-lguest.git
> This should be fairly clean: 45 lguest patches including the more generic
> drivers (aimed to be used by KVM as well, and hopefully others) and the start
> of separation of arch-specific from general lguest code.
> drivers/net/virtio_net.c | 435 +++++++++
> drivers/virtio/Kconfig | 8 +
> drivers/virtio/Makefile | 2 +
> drivers/virtio/config.c | 13 +
> drivers/virtio/virtio.c | 189 ++++
> drivers/virtio/virtio_ring.c | 313 +++++++
> drivers/block/virtio_blk.c | 308 +++++++
> drivers/char/virtio_console.c | 225 +++++
Having virtio in Linus tree would make my life easier wiring it up for
virtualization on s390.
For all virtio patches:
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
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.
next prev parent reply other threads:[~2007-10-23 6:55 UTC|newest]
Thread overview: 10+ 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:55 ` Christian Borntraeger [this message]
2007-10-23 7:44 ` Rusty Russell
2007-10-23 16:10 ` Linus Torvalds
2007-10-23 20:37 ` Jeff Garzik
2007-10-25 5:19 ` Rusty Russell
2007-10-25 6:31 ` Stephen Rothwell
2007-10-25 22:41 ` Linus Torvalds
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=200710230855.06253.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=hpa@zytor.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox