From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IGyuK-0003fM-Af for qemu-devel@nongnu.org; Fri, 03 Aug 2007 11:17:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IGyuE-0003dQ-MY for qemu-devel@nongnu.org; Fri, 03 Aug 2007 11:17:39 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IGyuE-0003dM-Hu for qemu-devel@nongnu.org; Fri, 03 Aug 2007 11:17:34 -0400 Received: from nz-out-0506.google.com ([64.233.162.230]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IGyuD-0003Mo-6G for qemu-devel@nongnu.org; Fri, 03 Aug 2007 11:17:33 -0400 Received: by nz-out-0506.google.com with SMTP id f1so1291968nzc for ; Fri, 03 Aug 2007 08:16:50 -0700 (PDT) Message-ID: Date: Fri, 3 Aug 2007 17:16:49 +0200 From: dragoran MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_101138_21871014.1186154209741" Subject: [Qemu-devel] merging kqemu into mainline kernel? 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 ------=_Part_101138_21871014.1186154209741 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, Is it planned to submit kqemu to lkml for inclusion into the mainline kernel? if not why? if yes any idea when? is it possible to try to get it in 2.6.24 ? ------=_Part_101138_21871014.1186154209741 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello,
Is it planned to submit kqemu to lkml for inclusion into the mainline kernel?
if not why?
if yes any idea when? is it possible to try to get it in 2.6.24 ?
------=_Part_101138_21871014.1186154209741--