This is predominantly for maintainers: I've noticed that there is a lot of code for btrfs ... and after few glimpses I've noticed that there are occurrences which beg for some refactoring to make it less of a pain to maintain. I'm speaking of occurrences where: - within a function there are multiple checks for null pointer and then whenever there is anything hanging on the end of that pointer to finally call the function, pass the pointer to it and watch it perform same checks to finally deallocate stuff on the end of a pointer. - single line functions ... called only in two places and so on. I know that you guys are busy, but maintaining code that is only growing must be a pain. -- 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
