From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ILkeg-0000zl-1m for qemu-devel@nongnu.org; Thu, 16 Aug 2007 15:05:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ILkeb-0000zY-IT for qemu-devel@nongnu.org; Thu, 16 Aug 2007 15:05:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ILkeb-0000zV-DC for qemu-devel@nongnu.org; Thu, 16 Aug 2007 15:05:09 -0400 Received: from nz-out-0506.google.com ([64.233.162.233]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ILkeb-00064n-BK for qemu-devel@nongnu.org; Thu, 16 Aug 2007 15:05:09 -0400 Received: by nz-out-0506.google.com with SMTP id f1so611475nzc for ; Thu, 16 Aug 2007 12:05:07 -0700 (PDT) Message-ID: <46d6db660708161205m28b0bce0w7d649d6cd31f9eb3@mail.gmail.com> Date: Thu, 16 Aug 2007 21:05:06 +0200 From: "Christian MICHON" Subject: Re: [Qemu-devel] merging kqemu into mainline kernel? In-Reply-To: <200708161531.52249.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200708161449.15732.paul@codesourcery.com> <779506c70708160702v52d1305u8d513b1dc9a81c98@mail.gmail.com> <200708161531.52249.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 8/16/07, Paul Brook wrote: > Yes, I mean the API. However in practice you'd probably want to try and share > the implementation as well. In short it's likely to need rewriting before > it's acceptable upstream. > > Paul > > P.S. Please don't top-post. Consider this your final warning. > blame it on gmail. this is the default behaviour. it's obviously not intended... -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu