From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmlR6-0008Lb-Nl for qemu-devel@nongnu.org; Wed, 21 Sep 2016 13:35:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bmlR2-0006j0-Iq for qemu-devel@nongnu.org; Wed, 21 Sep 2016 13:35:55 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34510) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bmlR2-0006ij-Cj for qemu-devel@nongnu.org; Wed, 21 Sep 2016 13:35:52 -0400 Date: Wed, 21 Sep 2016 20:35:49 +0300 From: "Michael S. Tsirkin" Message-ID: <20160921173549.o6jfzmiflu35g44y@redhat.com> References: <147446363181.4880.18104448248886932114.stgit@bahia> <20160921133428.250669.58191@ex-std-node742.prod.rhcloud.com> <20160921154433.48c307e1@bahia.lab.toulouse-stg.fr.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160921154433.48c307e1@bahia.lab.toulouse-stg.fr.ibm.com> Subject: Re: [Qemu-devel] [PATCH 0/7] virtio: avoid inappropriate QEMU termination List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Greg Kurz Cc: no-reply@ec2-52-6-146-230.compute-1.amazonaws.com, famz@redhat.com, qemu-devel@nongnu.org, kwolf@redhat.com, jasowang@redhat.com, mreitz@redhat.com, aneesh.kumar@linux.vnet.ibm.com, stefanha@redhat.com, cornelia.huck@de.ibm.com, pbonzini@redhat.com On Wed, Sep 21, 2016 at 03:44:33PM +0200, Greg Kurz wrote: > On Wed, 21 Sep 2016 06:35:04 -0700 (PDT) > no-reply@patchew.org wrote: > > > Hi, > > > > Your series failed automatic build test. Please find the testing commands and > > their output below. If you have docker installed, you can probably reproduce it > > locally. > > > > Heh... of course patchew doesn't know about Stefan's series. :) > > Is there an appropriate way to avoid complaints when sending a patchset that > isn't based on QEMU master ? It's a good idea to be explicit which tree does the patchset target, and on top of which patches it is applied. qemu master is kind of the default, but even then it's a good idea to tell everyone which hash it was based on - imagine someone trying to use your patchset several years from now. -- MST