> One last time: either post per-driver patches with all the cleanups for a driver > in a single patch, I preferred to offer source code adjustments according to specific transformation patterns mostly for each software module separately (also in small patch series). > or a per-directory patch (drivers/media/pci, usb, etc) doing the same cleanup > for all drivers in that directory. I am curious if bigger patch packages would be easier to get accepted. Or would you get frightened still by any other change combination? > I prefer the first approach, We have got different preferences for a safe patch granularity. > but it's up to you. I imagine that there are more development factors involved. > We don't have the time to wade through dozens of one-liner cleanup patches. It is usual that integration of update suggestions will take some time. How would the situation change if I would dare to regroup possible update steps? > I don't understand what is so difficult about this. There are communication difficulties to consider since your terse information from your conference meeting. If you would insist on patch squashing, would you dare to use a development tool like “quilt fold” also on your own once more? 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
