On Tue, Apr 27, 2010 at 04:02:28PM -0700, Greg KH wrote: > On Mon, Mar 29, 2010 at 12:34:28AM -0700, Joe Perches wrote: > > Make variables static where appropriate > > Rename dt3155_<foo_with_long_names> variables to dt_<foo_tla> > > to reduce code length and make more lines fit well in 80 chars > > Remove now unnecessary .h files > > Change indent to use tabs > > Remove unused functions > > Used bool more often > > Checkpatch clean > > This is too much in one patch, sorry. It also doesn't apply due to > other changes in these files (that you then remove in patch 3) from > other developers. > What I like is when people send in a patch that addresses all the white space issues at once. So from the above list it would probably fix these: > > to reduce code length and make more lines fit well in 80 chars > > Change indent to use tabs > > Checkpatch clean I have a script to check that a patch only changes whitespace and I can check that directly from mutt. It's in the my smatch repo: git://repo.or.cz/smatch.git under smatch_scripts/whitespace_only.sh If that passes and the source still compiles then I'm pretty sure it doesn't break anything. At that point I can look through it focusing on the whitespace instead of worrying that the patch introduces bugs. Once the whitespace is fixed the rest of the changes can be sent in separately and they're much smaller and easier to audit. regards, dan carpenter _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
