I wrote it the original way precisely for readability; it's easier, at least to me, to read and modify the old way. However, in my development version I happen to be printing a lot more stuff. To test, I collapsed 18 of my seq_printf's into one call. That reduced the function size by a couple hundred bytes. (Didn't do anything for the final kernel size though.) If it makes things better, even if only slightly, doesn't introduce bugs, and doesn't otherwise violate any other rules (correct me if I'm wrong), I would personally accept the minor readability tradeoff in this case. Acked-by: Richard Kuo <rkuo@xxxxxxxxxxxxxx> On Fri, Oct 21, 2016 at 08:50:11PM +0200, SF Markus Elfring wrote: > > When the author of the semantic patch language is telling you to stand down, > > The collaboration evolved between Julia and me during the years somehow. > Different software development opinions occur then as usual. > Further opinions from contributors like you can eventually show variations > between disagreement and acceptance. > > > > and you still want to try to argue for blind application of patches, > > I guess that we have got different views about "blind" tries. > > > > we have a really big problem. > > I hope that potential communication difficulties can still be resolved. > > > > Especially when some of your patches have actually introduced bugs. > > I assume that these incidents could be clarified further, couldn't they? > > Regards, > Markus > -- > To unsubscribe from this list: send the line "unsubscribe linux-hexagon" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
