Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > On Wed, 2014-02-05 at 19:44 -0600, Calvin Owens wrote: >> Create a function to return a descriptive string for each reason code, >> and print that instead of the numeric value in the kernel log. These >> codes are easily found on popular search engines, but one is generally >> not able to access the internet when dealing with wireless connectivity >> issues. > > I believe both iw and wpa_supplicant already have the reason code > printout, and if you're diagnosing connectivity issues then you're > probably using those anyway (e.g. iw event -t), so I don't really see > much point in adding this to the kernel? FWIW I find this useful. When I have connection problems I rarely look at wpasupplicant, mostly I'm so lazy that I just check from the kernel log what's happening. Just my 0.02 EUR. -- Kalle Valo -- 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
