>> Although it fixes it for building on 32 bit architectures,
>> won't changing
>>
>> __u64 uid = 0xFFFFFFFFFFFFFFFF;
>>
>> to
>>
>> __u64 uid = 0xFFFFFFFFFFFFFFFFULL;
>>
>> generate a type mismatch warning on ppc64 and similar 64
>> bit architectures since __u64 is not a unsigned long long
>> on ppc64 (it is unsigned long)?
> u64 uid = -1;
>
> will work just nicely.
Won't that generate a warning about assigning a signed quantity
to an unsigned variable?
What's really needed is a set of definitions along the lines of
#define MAX_U32 ((__u32) 0xFFFFFFFFUL)
#define MAX_U64 ((__u64) 0xFFFFFFFFFFFFFFFFULL)
but as an intermediate measure, how about...
__u64 uid = ((__u64) 0xFFFFFFFFFFFFFFFFULL);
Best wishes from Riley.
--- * Nothing as pretty as a smile, nothing as ugly as a frown.
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 5-Jun-2003- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/