From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] qemu-kvm: Add CPUID support for VIA CPU Date: Fri, 06 May 2011 12:25:46 +0200 Message-ID: <4DC3CCAA.5020100@siemens.com> References: <4DC255A7.1000200@siemens.com> <4DC3A840.7040906@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "avi@redhat.com" , "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" , "KaryJin@viatech.com.cn" To: "BrillyWu@viatech.com.cn" Return-path: Received: from thoth.sbs.de ([192.35.17.2]:28565 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751757Ab1EFKZx (ORCPT ); Fri, 6 May 2011 06:25:53 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 2011-05-06 11:37, BrillyWu@viatech.com.cn wrote: > >>> >>> If I want to submit a patch for the qemu-kvm-git, should I >> use "[QEMU-DEVEL][Patch]..." as the subject? Or there are other rules >> for qemu-kvm upstream? If yes, would you like to tell me?. Thanks! >> >> If you really have to target qemu-kvm only, then you tagging is fine. >> But this patch does not qualify for such exclusiveness. >> Rather, your feature should go into upstream's KVM first and will then >> be merged back into qemu-kvm on next update. > > I have submit a patch into upstream's KVM for supporting these features before, and the patch has been applied in kvm-git. As far as I can see, nothing has been applied to any tree, neither qemu.git nor qemu-kvm.git. > Do you mean that I should not submit this patch until the KVM's patch is merged back? You still need to submit a fixed version of this patch against qemu-kvm.git, uq/master branch (which is qemu.git effectively). Then Marcelo or Avi can pick it up and push it to upstream. Once it's merged there, qemu-kvm.git will update from upstream, and you will have your patch applied to both trees. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux