From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
netdev@vger.kernel.org, Anthony Liguori <aliguori@us.ibm.com>,
Dor Laor <dor.laor@qumranet.com>
Subject: Re: virtio_net and SMP guests
Date: Fri, 11 Jan 2008 20:53:00 +1100 [thread overview]
Message-ID: <200801112053.01861.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200801101651.58908.borntraeger@de.ibm.com>
On Friday 11 January 2008 02:51:58 Christian Borntraeger wrote:
> What about the following patch:
Looks correct and in fact pretty orthodox.
I've folded this in, thanks!
Rusty.
prev parent reply other threads:[~2008-01-11 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200712141312.05562.borntraeger@de.ibm.com>
[not found] ` <200801101337.40433.borntraeger@de.ibm.com>
[not found] ` <200801101639.15995.borntraeger@de.ibm.com>
2008-01-10 15:51 ` virtio_net and SMP guests Christian Borntraeger
2008-01-11 9:53 ` 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=200801112053.01861.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).