On 10/03/2012 08:07 AM, Dan Carpenter wrote:
Sparse complains that we use zero instead of NULL here. In fact, the initialization is wrong and should be removed. Doing these kinds of bogus initializations means that GCC can't detect unitialized variables and leads to bugs.
We already had it fixed internally, but your change is more sensible. I had it reviewed internally and plan to send it to John for 3.8 (ie. wireless-next after merge window). Let me know if that is ok with you.
Gr. AvS -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
