There is only 2 rules in kernel development which you can't break:
1. Kernel APIs to userland are always backwards compatible
2. If you break something, you will take responsibility
If maintainer breaks both of those rules, how can you accept patches from him/her ever again? Remember that amount of patches handled by kernel core team is enormous, you have to able to trust subsystem maintainers at least some degree. In corporate world this would have caused immediate "clear your desk" reaction.
1. Kernel APIs to userland are always backwards compatible
2. If you break something, you will take responsibility
If maintainer breaks both of those rules, how can you accept patches from him/her ever again? Remember that amount of patches handled by kernel core team is enormous, you have to able to trust subsystem maintainers at least some degree. In corporate world this would have caused immediate "clear your desk" reaction.