On Fri, 25 Jan 2008, Michael Buesch wrote: > > I'm not sure what's so hard about adding this trivial fix to the firmware. > The _fact_ that this warning triggered for lots of drivers means that > developers are not aware of the problem. So why should we go on hiding bugs > that are _trivial_ to fix? .. mainly because I don't think it's a bug in the network driver. It really sounds like you're creating a warning for a bug in the wireless infrastructure, and then trying to blame the drivers that don't agree with that warning being valid in the first place. > I absolutely hate the attitude "The problem does not happen on most > of the stuff intel uses, so they don't need to fix this". That's not *my* attitude at least. My attitude is: CPU's that do unaligned accesses right are the *good* CPU's. We should encourage them, and put the onus of being crap on the ones that are crap, rather than penalizing the ones that aren't. In other words, we should use "get_unaligned()". Linus - 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
