Re: [PATCH 2/3] netlink: the temp variable name max is ambiguous

From: Denis Cheng <[email protected]>
Date: Sun,  2 Sep 2007 03:45:58 +0800

> with the macro max provided by <linux/kernel.h>, so changed its name to a more proper one: limit
> 
> Signed-off-by: Denis Cheng <[email protected]>

Not strictly necessary because CPP knows to differentiate between
'max(' and plain 'max' when evaluating if a CPP macro should be
expanded or not.

Nonetheless, applied to net-2.6.24, thanks.
-
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 2/3] netlink: the temp variable name max is ambiguous
  - From: "rae l" <[email protected]>

References:
- [PATCH 1/3] netlink: use the macro min(x,y) provided by <linux/kernel.h> instead
  - From: Denis Cheng <[email protected]>
- [PATCH 2/3] netlink: the temp variable name max is ambiguous
  - From: Denis Cheng <[email protected]>

Prev by Date: Re: [PATCH 1/3] netlink: use the macro min(x,y) provided by <linux/kernel.h> instead
Next by Date: Re: [PATCH]PCI:disable resource decode in PCI BAR detection
Previous by thread: Re: [PATCH 3/3] netlink: use a statically allocated nl_table instead
Next by thread: Re: [PATCH 2/3] netlink: the temp variable name max is ambiguous
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]