From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:52281) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TrEWy-0005Wv-9e for qemu-devel@nongnu.org; Fri, 04 Jan 2013 16:10:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TrEWv-0007ZH-M8 for qemu-devel@nongnu.org; Fri, 04 Jan 2013 16:10:20 -0500 Received: from e9.ny.us.ibm.com ([32.97.182.139]:52375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TrEWv-0007ZC-Hw for qemu-devel@nongnu.org; Fri, 04 Jan 2013 16:10:17 -0500 Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 4 Jan 2013 16:10:16 -0500 Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 2A83D38C8054 for ; Fri, 4 Jan 2013 16:10:15 -0500 (EST) Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r04LAElL312306 for ; Fri, 4 Jan 2013 16:10:14 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r04LAEEb016594 for ; Fri, 4 Jan 2013 19:10:14 -0200 From: Anthony Liguori In-Reply-To: <20130104204851.GU18372@otherpad.lan.raisama.net> References: <1357313864-31026-1-git-send-email-ehabkost@redhat.com> <201301042020.r04KKv0R014816@d01av02.pok.ibm.com> <20130104204851.GU18372@otherpad.lan.raisama.net> Date: Fri, 04 Jan 2013 15:10:09 -0600 Message-ID: <87a9sofydq.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH 0/9] target-i386: make "enforce" flag work as it should List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: qemu-devel@nongnu.org Eduardo Habkost writes: > The Cc header of the message looks broken. It contained: > > Cc: > =?utf-8?q?kvm=40vger=2Ekernel=2Eorg=2C_Gleb_Natapov_=3Cgleb=40redhat=2E?=.=?utf-8?q?com=3E=2C_libvir-list=40redhat=2Ecom=2C_Marcelo_Tosatti_=3Cmtosat?=.=?utf-8?q?ti=40redhat=2Ecom=3E=2C_Igor_Mammedov_=3Cimammedo=40redhat=2Ecom?=.=?utf-8?q?=3E=2C_Jiri_Den Yes, email sucks :-( I'm working to fix it... sorry for the noise. > > On Fri, Jan 04, 2013 at 08:21:22PM -0000, Anthony Liguori wrote: >> Hi, >> >> This is an automated message generated from the QEMU Patches. >> Thank you for submitting this patch. This patch no longer applies to qemu.git. > > Cool. :-) > >> >> This may have occurred due to: >> >> 1) Changes in mainline requiring your patch to be rebased and re-tested. >> >> 2) Sending the mail using a tool other than git-send-email. Please use >> git-send-email to send patches to QEMU. >> >> 3) Basing this patch off of a branch that isn't tracking the QEMU >> master branch. If that was done purposefully, please include the name >> of the tree in the subject line in the future to prevent this message. >> >> For instance: "[PATCH block-next 1/10] qcow3: add fancy new feature" > > What should I do if the patch requires other patches that are on the > mailing list but no git tree yet? That was the case, here (the series > depends on the disable-kvm_mmu_op series I sent previously today). Good question. In this case, just say [PATCH qom-cpu...] since this is against the qom-cpu tree. Or even an RFC tag if that's appropriate. I wouldn't recommend sending patches meant for merging that depend on other series still on the list without an RFC tag. For no other reason that you'll likely confuse someone trying to apply it. Regards, Anthony Liguori > >> >> 4) You no longer wish for this patch to be applied to QEMU. No additional >> action is required on your part. >> >> Nacked-by: QEMU Patches >> >> Below is the output from git-am: >> >> Applying: target-i386: kvm: -cpu host: Use GET_SUPPORTED_CPUID for SVM features >> Applying: target-i386: kvm: Enable all supported KVM features for -cpu host >> Applying: target-i386: check/enforce: Fix CPUID leaf numbers on error messages >> fatal: sha1 information is lacking or useless (target-i386/cpu.c). >> Repository lacks necessary blobs to fall back on 3-way merge. >> Cannot fall back to three-way merge. >> Patch failed at 0003 target-i386: check/enforce: Fix CPUID leaf numbers on error messages >> The copy of the patch that failed is found in: >> /home/aliguori/.patches/qemu-working/.git/rebase-apply/patch >> When you have resolved this problem run "git am --resolved". >> If you would prefer to skip this patch, instead run "git am --skip". >> To restore the original branch and stop patching run "git am --abort". >> > > -- > Eduardo