Re: [PATCH -mm] Introduce U16_MAX and U32_MAX

On Tue, 31 Jul 2007 21:56:12 +0530 (IST)
Satyam Sharma <[email protected]> wrote:

> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -30,6 +30,9 @@ extern const char linux_proc_banner[];
>  #define LLONG_MIN	(-LLONG_MAX - 1)
>  #define ULLONG_MAX	(~0ULL)
>  
> +#define U16_MAX		((u16) ~0U)
> +#define U32_MAX		((u32) ~0U)
> +

hm, I'd have thought that there's a risk of gcc warnings here, forcing
0xffffffff into a u16, but apparently not.

Still, I think it'd be tidier here to tell the truth and use plain
old 0xffff and 0xffffffff?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH -mm] Introduce U16_MAX and U32_MAX
    • From: Satyam Sharma <[email protected]>
  • Re: [PATCH -mm] Introduce U16_MAX and U32_MAX
    • From: Jan Engelhardt <[email protected]>

• References:
  • [PATCH -mm] Introduce U16_MAX and U32_MAX
    • From: Satyam Sharma <[email protected]>

• Prev by Date: Re: Inclusion of vmware mptbase regression fix
• Next by Date: Re: [PATCH -mm] Introduce strtol_check_range()
• Previous by thread: [PATCH -mm] Introduce U16_MAX and U32_MAX
• Next by thread: Re: [PATCH -mm] Introduce U16_MAX and U32_MAX
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]