From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] Introduce QEMU_NEW() Date: Mon, 25 Jul 2011 15:41:46 +0300 Message-ID: <4E2D648A.6080305@redhat.com> References: <1311583872-362-1-git-send-email-avi@redhat.com> <4E2D5D7C.40208@codemonkey.ws> <4E2D5F0D.2040303@redhat.com> <4E2D5FB3.7000906@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org To: Anthony Liguori Return-path: In-Reply-To: <4E2D5FB3.7000906@codemonkey.ws> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 07/25/2011 03:21 PM, Anthony Liguori wrote: > On 07/25/2011 07:18 AM, Avi Kivity wrote: >> On 07/25/2011 03:11 PM, Anthony Liguori wrote: >>> On 07/25/2011 03:51 AM, Avi Kivity wrote: >>>> qemu_malloc() is type-unsafe as it returns a void pointer. Introduce >>>> QEMU_NEW() (and QEMU_NEWZ()), which return the correct type. >>> >>> Just use g_new() and g_new0() >>> >> >> These bypass qemu_malloc(). Are we okay with that? > > Yes. We can just make qemu_malloc use g_malloc. > Excellent. Patch withdrawn. -- error compiling committee.c: too many arguments to function