It seems like the best approach would be to have a path (through kernel newbies and/or kernel janitors and thence through a small group of volunteer liaisons to the main kernel list. Then all the clean-up patches can be consolidated, reviewed tested and merged in a streamlined manner. Perhaps one technique could be for new (substantive) patches to go through LKML -- then to testing -- then through the janitorial process (which adds the stylistic and cosmetic clean-up) --- then back through testing (-mm or similar kernels) and finally back through LKML on its way to main. In that model the janitorial team keeps their clean-up patches in their own repository, in holding, and merges the clean-ups with substantive patches as those arise. Occassionally they inject a separate patch to a messy but long untouched area of the sources --- but it's all coming from them and done in a way that doesn't burn out the LKML participants. (So such clean-up only injections can be done opportunistically when the list has been relatively quiet for a few days). Just a thought. JimD
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds