This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH 0 of 4] libxl: use libxl__ namespace for hidden funct

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0 of 4] libxl: use libxl__ namespace for hidden functions
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Tue, 07 Sep 2010 11:07:52 +0100
Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Tue, 07 Sep 2010 03:08:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
As described in libxl.h header internal functions should use the
libxl__ namespace.

I'm not sure this churn is worth it but we are starting to see patches
adding internal functions which do not follow the convention and it is
hard to ask for a respin with a straight face when there is so much
existing dirty laundry so we should either obey the documented
convention or ditch it.

I didn't touch flexarrays or xs_writev which is something of a special
case for use in dm_xenstore_record_pid (libxl__xs_writev already
exists but isn't immediately suitable for use).

Xen-devel mailing list