On Mon, Mar 2, 2009 at 6:02 PM, Alina Friedrichsen <x-alina@xxxxxxx> wrote: > > I personally think with the "& 0xffffffff" it's cleaner, because it's type > independent. And the compiler should optimize it out, if the type is really > 32 bit wide. Yes, the compiler will optimize it out, but it looks noisy to me. It's declared u64 one line above so it is clearly a no-op... I guess it is a personal taste thing. > This is an old patch, I now use git for it. Ok, thanks! I only mentioned it because I wanted to see the parameters and had to go back to the code. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
