Peter Stuge wrote: > It is not very wise for ath9k to reduce debug output with the > motivation that some users leave it enabled even if they deploy > into limited systems and they would actually prefer to have less > debugging. > > If ath9k users have an issue with debugging being too big then THEY > can disable it. It seems senseless to delete debugging when the > driver is clearly still buggy. > > It also seems senseless to try to punt to mac80211. It is amazing > that Ben's point is not absolutely obvious. > > One purpose of debugging is to allow and enable consistency checking. > Redundant information is by definition neccessary for that. > > > As a compromise, you could suggest a move to a two-level compile time > option for debugging. You would enable only what you believe to be > adequate for debugging in production systems (wait, what did I just > write? oh well..) with the first option, and you would allow the rest > of the world to enable complete debugging with the second option. /me disregards all the nerd-rage and the general snarkiness. Having multiple levels of debugging makes things complex. If the general consensus is to keep the information, I can rework the patch. Sujith -- 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
