On 23 September 2016 at 09:50, SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx> wrote: >> Markus, please contact the list in advance in future before posting a bunch >> of patches that don't fix any problems. > > I am trying to improve various open issues also in Linux source files. > That the fact that you see issues (in these particular cases) while others do not indicates that the commit summary could be explained better. A good commit summary should provide enough information to do that and make people _want_ the patch. From my limited experience through your patches (just skimmed a few) you seems to be describing what the patch does as opposed to why it does it and why should one find it interesting/wanted. You might want to read through the following [1] [2] and many others that exist out there. -Emil [1] http://chris.beams.io/posts/git-commit/ [2] http://who-t.blogspot.fi/2009/12/on-commit-messages.html _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
