On Mon, 2007-03-05 at 00:52 +0100, Johannes Berg wrote: > Wouldn't you just always have prism headers in monitor mode? All cards I > know do that iirc. Or well, radiotap seems to be the format of fashion > these days. I don't particularly like either :) Sounds good. Radiotap is more flexible and better defined, but just leaving prism headers for now would be fine. > Not sure. I find that it messes up some things too. Maybe run Lindent, > diff the original vs. the result and take the hunks you like. Yes, something like that. > > * istate should be accessed using atomic_set/atomic_read; locking is overkill > > atomic operations can be quite expensive too, but you probably know > better if you need it or not. Actually, it looks like we don't need them either. Atomic operations are useful for counters or generally when data is read and written at once. Simply reading and writing integers is atomic by design of any sane and supported CPU. The istate locks were causing complains from the lock checkers, and my attempt to replace them with atomic operations silenced those complaints. But It looks like we just need to drop those locks. They were put there in a hurry without due checking, they don't address any problem, but they may create one. -- Regards, Pavel Roskin - 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
