linux.conf.au, January 2003
      POLITICS: Style

Revolutionary changes have been most successful when they are small (at least to begin with)

The correct way to write a portable driver is to write it for 2.5, and then use compatibility macros for 2.4 and 2.2.

Removal of debugging stuff: if it's only useful to the maintainer, get rid of it before submission.

Standards are much higher for core code and infrastructure then drivers and other code which doesn't break anything else.