From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60050) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WwzNy-0000St-G7 for qemu-devel@nongnu.org; Tue, 17 Jun 2014 15:49:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WwzNs-0001Ed-CG for qemu-devel@nongnu.org; Tue, 17 Jun 2014 15:49:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7463) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WwzNs-0001EZ-35 for qemu-devel@nongnu.org; Tue, 17 Jun 2014 15:49:32 -0400 Date: Tue, 17 Jun 2014 22:49:53 +0300 From: "Michael S. Tsirkin" Message-ID: <20140617194953.GG15610@redhat.com> References: <1403021756-15960-1-git-send-email-mst@redhat.com> <1403021756-15960-12-git-send-email-mst@redhat.com> <53A08B64.4050605@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL 011/103] pc-dimm: do not allow to set already used memdev List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Vasilis Liaskovitis , Anthony Liguori , Peter Crosthwaite , Igor Mammedov On Tue, Jun 17, 2014 at 07:45:10PM +0100, Peter Maydell wrote: > On 17 June 2014 19:39, Eric Blake wrote: > > On 06/17/2014 11:36 AM, Michael S. Tsirkin wrote: > >> From: Igor Mammedov > >> > >> using the same memdev backend more than once will cause > >> assersion at MemoryRegion mapping time becase it's already > > > > s/assersion/assertion/; s/becase/because/ > > (but probably too late now that this is a pull request) > > Incidentally, if anybody notices something that should > mean a pull request ought not to be applied, they need > to send an email which is a followup to the cover letter. > Otherwise there's no guarantee I'll notice it when I'm > processing the pullreq. > > thanks > -- PMM Right. Though that's kind of creating the wrong incentive for people - why bother reviewing patches on list, I can check what's being pulled ;) So note it needs to be something very serious, like a crash for most users on a major platform. Issues that affect minority of users, warnings, error handling errors can be fixed in follow up patches. And sending Acks in response to the pull request is definitely not helpful :) -- MST