From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49811) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fa6c0-0005Er-UG for qemu-devel@nongnu.org; Mon, 02 Jul 2018 17:43:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fa6bx-0002ac-Kn for qemu-devel@nongnu.org; Mon, 02 Jul 2018 17:43:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36162) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fa6bx-0002aF-Em for qemu-devel@nongnu.org; Mon, 02 Jul 2018 17:43:53 -0400 Date: Mon, 2 Jul 2018 18:43:45 -0300 From: Eduardo Habkost Message-ID: <20180702214345.GI7451@localhost.localdomain> References: <20180702094152.7882-1-david@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180702094152.7882-1-david@redhat.com> Subject: Re: [Qemu-devel] [PATCH v1] machine: properly free device_memory List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Hildenbrand Cc: qemu-devel@nongnu.org, Igor Mammedov , Marcel Apfelbaum On Mon, Jul 02, 2018 at 11:41:52AM +0200, David Hildenbrand wrote: > Machines might have inititalized device_memory if they support memory > devices, so let's properly free it. > > Signed-off-by: David Hildenbrand Queued, thanks. -- Eduardo