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

Re: [Xen-devel] [patch] [3/3] dom0_ops explicitly sized types

To: Hollis Blanchard <hollisb@xxxxxxxxxx>
From: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Date: Thu, 25 May 2006 18:39:57 +0300
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 25 May 2006 11:44:52 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Wed, May 24, 2006 at 06:04:34PM -0500, Hollis Blanchard wrote:

> Replace 'long' in the dom0_ops and privcmd structures with uint64_t.

I am all in favor of identifying interfaces using explicitly sized
types. The standard kernel style is to use u64 not uint64_t though.

Cheers,
Muli

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Follow-Ups:
- Re: [Xen-devel] [patch] [3/3] dom0_ops explicitly sized types
  - From: Hollis Blanchard

References:
- [Xen-devel] [patch] [3/3] dom0_ops explicitly sized types
  - From: Hollis Blanchard

Prev by Date: Re: [Xen-devel] Xenoprof in an HVM domain
Next by Date: RE: [Xen-devel] windows user mode debugging under xen
Previous by thread: [Xen-devel] [patch] [3/3] dom0_ops explicitly sized types
Next by thread: Re: [Xen-devel] [patch] [3/3] dom0_ops explicitly sized types
Index(es):
- Date
- Thread

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