Milind Arun Choudhary wrote:
why bitops.h? coz BIT qualifies for a "bitop"
& bitops.h is inclued by kernel.h, hence accessible from every part
of the tree without mucb efforts
I don't think there is anyone who objects to this
c>but it is not sutaible for those who want to go beyond this limit,
as they will not be warned
And this is the reason for this overly long thread :)
So all we need is people to be carefull before passing anything to BIT
This is the difficult thing to do
so now i think it should be ok to have
#define BIT(nr) (1UL << ((nr) % BITS_PER_LONG))
#define LLBIT(nr) (1ULL << (nr))
thoughts
Since you guys seems in agreement about the silenced compiler-warnings,
then I will rest my case.
Richard Knutsson
-
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/
[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]
