Would I step on anyone’s toes if I started submitting some extra patches to increase the verbosity of the BTRFS code in the kernel log? I would probably start with most things as pr_debug just to keep it quiet on non-debug kernels, but I just thought that it might add a great deal of clarity to the code base and maybe help sysadmins figure out what is a BTRFS issue and what is some other issue. I have read through the Developer, SubmittingPatches, and Coding Style. I am at peace with git. I am not promising everything done, but what I can help with doing, I will do. As of right now there are: 36 pr_ 323 WARN_ON 506 BUG_ON 107,197 lines of code -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
