[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1337792083.9783.34.camel@laptop>
Date: Wed, 23 May 2012 18:54:43 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Borislav Petkov <borislav.petkov@....com>
Cc: "H. Peter Anvin" <hpa@...or.com>, mingo@...nel.org,
linux-kernel@...r.kernel.org, frank.arnold@....com,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
tglx@...utronix.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/mce] x86/bitops: Move BIT_64() for a wider use
On Wed, 2012-05-23 at 18:29 +0200, Peter Zijlstra wrote:
> If I remember my type rules correctly you'll get something like that
> with:
>
> #define BIT(n) ({ typeof(n) __n = (n); (__n < 32) ? (1UL << __n) : (1ULL << __n); })
OK, that doesn't work. Memory played tricks on me. Now I'll keep
wondering what was special about ?: and how I've seen it abused.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists