On Mon, Aug 10, 2015 at 09:38:56PM +0300, Dan Carpenter wrote: > Warnings are not a bad thing they are a valuable marker to let us know > which code is broken. If we just silence the warning in the laziest > possible way then we are throwing away valuable information. It's > better to leave the warning there so that the next person can fix it > properly. > > If you want to leave the code as-is that is absolutely fine with me, but > don't remove the warning until someone can look at this a bit carefully. > > regards, > dan carpenter >
Thank you. It looks like it needs more knowledge of wireless networking to conclude if there was any problem and to fix if any problem exists. I will come back to this problem in near future, if the error was still observed then. chandra -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
