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

Re: [Xen-devel] [PATCH v2 1/8] tools: libxl: use uint64_t not unsigned long long for addresses

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Wed, 30 Apr 2014 16:49:46 +0100
Cc: stefano.stabellini@xxxxxxxxxxxxx, tim@xxxxxxx, julien.grall@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxx
Delivery-date: Wed, 30 Apr 2014 15:49:59 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Wed, 2014-04-30 at 16:12 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH v2 1/8] tools: libxl: use uint64_t not unsigned 
> long long for addresses"):
> > Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
> 
> If we are going to be doing this, why not introduce a type alias or
> two ?

Good point. I'll do that.

Ian.



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

References:
- [Xen-devel] [PATCH v2 0/8] xen: arm: support up to (almost) 1TB of guest RAM
  - From: Ian Campbell
- [Xen-devel] [PATCH v2 1/8] tools: libxl: use uint64_t not unsigned long long for addresses
  - From: Ian Campbell
- Re: [Xen-devel] [PATCH v2 1/8] tools: libxl: use uint64_t not unsigned long long for addresses
  - From: Ian Jackson

Prev by Date: Re: [Xen-devel] Hit ASSERT in kill_timer function
Next by Date: [Xen-devel] [linux-next test] 26090: tolerable trouble: blocked/broken/fail/pass
Previous by thread: Re: [Xen-devel] [PATCH v2 1/8] tools: libxl: use uint64_t not unsigned long long for addresses
Next by thread: [Xen-devel] [PATCH v2 2/8] tools: arm: report an error if the guest RAM is too large
Index(es):
- Date
- Thread

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