From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/7] AlacrityVM guest drivers Reply-To: Date: Thu, 06 Aug 2009 16:44:03 +0300 Message-ID: <4A7ADE23.5010208@redhat.com> References: <20090803171030.17268.26962.stgit@dev.haskins.net> <20090806081955.GA9752@redhat.com> <4A7A8F7B0200005A00051B84@sinclair.provo.novell.com> <4A7AD29E.50800@redhat.com> <4A7A9C6B0200005A00051BB9@sinclair.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alacrityvm-devel@lists.sourceforge.net, "Michael S. Tsirkin" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: Gregory Haskins Return-path: In-Reply-To: <4A7A9C6B0200005A00051BB9@sinclair.provo.novell.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 08/06/2009 04:03 PM, Gregory Haskins wrote: >> It's true that vbus is a separate project (in fact even virtio is >> completely separate from kvm). Still I think it would be of interest to >> many kvm@ readers. >> > > Well, my goal was to not annoy KVM readers. ;) So if you feel as though there is benefit to having all of KVM CC'd and I won't be annoying everyone, I see no problem in cross posting. > I can only speak for myself, I'm interested in this project (though still rooting for virtio). > Would you like to see all conversations, or just ones related to code (and, of course, KVM relevant items) I guess internal vbus changes won't be too interesting for most readers, but new releases, benchmarks, and kvm-related stuff will be welcome on the kvm list. -- error compiling committee.c: too many arguments to function