Re: Clarification for general change acceptance

2017-05-12 Thread SF Markus Elfring
> When you make a patch, you are not obliged to eliminate all of the other > checkpatch warnings on the file. Your view is generally fine. > I don't know where you got this idea from. I got used as a professional software developer to some approaches for reducing development warnings to some de

Re: Clarification for general change acceptance

2017-05-12 Thread Julia Lawall
> But I will come along source code places where I am going to update details > which are also trivial. When you make a patch, you are not obliged to eliminate all of the other checkpatch warnings on the file. I don't know where you got this idea from. The submitting patch guidelines don't say t

Re: Clarification for general change acceptance

2017-05-12 Thread SF Markus Elfring
> Developer reputation matters for somewhat controversial > patches being applied as well as non-controversial and > obviously correct patches being ignored. I am aware that there are more factors involved. > Your reputation means most all of your patches fall into > the latter category. I hope