> What I should do really is ask you to take all similar (remove error > message, don't use sizeof(struct X), remove '== NULL') changes and > squash them into single patches. I would try such an approach more often if I would get also more promising indications of corresponding change acceptance besides other software development “surprises”. > However, I realise that you might want the "upstream creds", > so I won't do that I find this view interesting somehow. > -- but not at the expense of my time/effort. > > The two choices are to squash or to create a set. This information triggers recurring difficulties around differences in the preferred patch granularity. Regards, Markus -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
