[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions

To: Dario Faggioli <raistlin@xxxxxxxx>
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 26 Jun 2012 17:06:13 +0100
Cc: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Tue, 26 Jun 2012 16:06:32 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Tue, 2012-06-26 at 17:01 +0100, Dario Faggioli wrote:
> Specifying they allocate dynamic memory that needs to be explicitly freed.
> 
> Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx>

Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions
  - From: Ian Jackson

References:
- [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions
  - From: Dario Faggioli

Prev by Date: [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions
Next by Date: Re: [Xen-devel] [PATCH] tools/hotplug: fix locking
Previous by thread: [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions
Next by thread: Re: [Xen-devel] [PATCH v2] libxl: document the memory ownership of some functions
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.